[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4537af8d-e28f-1c27-53a9-e3208874037e@suse.com>
Date: Wed, 19 Feb 2020 10:46:15 +0100
From: Jürgen Groß <jgross@...e.com>
To: Thomas Gleixner <tglx@...utronix.de>,
xen-devel@...ts.xenproject.org, x86@...nel.org,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org
Cc: Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Hellstrom <thellstrom@...are.com>,
"VMware, Inc." <pv-drivers@...are.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Stefano Stabellini <sstabellini@...nel.org>,
stable@...r.kernel.org
Subject: Re: [PATCH] x86/ioperm: add new paravirt function update_io_bitmap
On 19.02.20 10:22, Thomas Gleixner wrote:
> Jürgen Groß <jgross@...e.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
Powered by blists - more mailing lists