On 19.02.20 10:22, Thomas Gleixner wrote:
Jürgen Groß jgross@suse.com writes:
On 18.02.20 22:03, Thomas Gleixner wrote:
BTW, why isn't stuff like this not catched during next or at least before the final release? Is nothing running CI on upstream with all that XEN muck active?
This problem showed up by not being able to start the X server (probably not the freshest one) in dom0 on a moderate aged AMD system.
Our CI tests tend do be more text console based for dom0.
tools/testing/selftests/x86/io[perm|pl] should have caught that as well, right? If not, we need to fix the selftests.
Hmm, yes. Thanks for the pointer.
Will ask our testing specialist what is done in this regard and how it can be enhanced.
Juergen