From: Thomas Gleixner <tglx@linutronix.de>
To: xen-devel@lists.xenproject.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: Juergen Gross <jgross@suse.com>,
Thomas Hellstrom <thellstrom@vmware.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"VMware, Inc." <pv-drivers@vmware.com>,
stable@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] x86/ioperm: add new paravirt function update_io_bitmap
Date: Tue, 18 Feb 2020 22:03:09 +0100 [thread overview]
Message-ID: <87mu9fr4ky.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200218154712.25490-1-jgross@suse.com>
Juergen Gross <jgross@suse.com> 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 <jbeulich@suse.com>
> Cc: <stable@vger.kernel.org> # 5.5
> Signed-off-by: Juergen Gross <jgross@suse.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> Tested-by: Jan Beulich <jbeulich@suse.com>
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
next prev parent reply other threads:[~2020-02-18 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 15:47 [PATCH] x86/ioperm: add new paravirt function update_io_bitmap Juergen Gross
2020-02-18 21:03 ` Thomas Gleixner [this message]
2020-02-19 5:35 ` Jürgen Groß
2020-02-19 8:29 ` Jan Beulich
2020-02-19 9:22 ` Thomas Gleixner
2020-02-19 9:46 ` Jürgen Groß
2020-02-28 15:35 ` Jürgen Groß
2020-02-28 17:47 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mu9fr4ky.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pv-drivers@vmware.com \
--cc=sstabellini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=thellstrom@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).