From: Thomas Gleixner Subject: Re: [PATCH] x86/ioperm: add new paravirt function update_io_bitmap Date: Tue, 18 Feb 2020 22:03:09 +0100 Message-ID: <87mu9fr4ky.fsf@nanos.tec.linutronix.de> References: <20200218154712.25490-1-jgross@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20200218154712.25490-1-jgross@suse.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: virtualization-bounces@lists.linux-foundation.org Sender: "Virtualization" To: xen-devel@lists.xenproject.org, x86@kernel.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org Cc: Juergen Gross , Thomas Hellstrom , Stefano Stabellini , "VMware, Inc." , stable@vger.kernel.org, Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , Boris Ostrovsky List-Id: virtualization@lists.linuxfoundation.org Juergen Gross writes: > Commit 111e7b15cf10f6 ("x86/ioperm: Extend IOPL config to control > ioperm() as well") reworked the iopl syscall to use I/O bitmaps. > > Unfortunately this broke Xen PV domains using that syscall as there > is currently no I/O bitmap support in PV domains. > > Add I/O bitmap support via a new paravirt function update_io_bitmap > which Xen PV domains can use to update their I/O bitmaps via a > hypercall. > > Fixes: 111e7b15cf10f6 ("x86/ioperm: Extend IOPL config to control ioperm() as well") > Reported-by: Jan Beulich > Cc: # 5.5 > Signed-off-by: Juergen Gross > Reviewed-by: Jan Beulich > Tested-by: Jan Beulich Duh, sorry about that and thanks for fixing it. 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? Thanks, tglx