LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jim Mattson <jmattson@google.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Wanpeng Li" <kernellwp@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"kvm list" <kvm@vger.kernel.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Tim Shearer" <tshearer@advaoptical.com>,
"Liran Alon" <liran.alon@oracle.com>
Subject: Re: [PATCH 2/3] KVM: X86: Allow userspace to disable ioport intercept
Date: Tue, 15 May 2018 14:56:41 -0700 [thread overview]
Message-ID: <CALMp9eT5aD0tjdTzTABo5a0aEtB52bZ7_-PCTF35Tikf8Q-vDg@mail.gmail.com> (raw)
In-Reply-To: <20180511154359.GC26700@char.us.oracle.com>
I'd prefer to let the kvm module have the final say as to whether or
not to allow userspace to do this.
On Fri, May 11, 2018 at 8:43 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Fri, May 11, 2018 at 11:42:46AM -0400, Konrad Rzeszutek Wilk wrote:
>> On Mon, Apr 16, 2018 at 10:46:01PM -0700, Wanpeng Li wrote:
>> > From: Wanpeng Li <wanpengli@tencent.com>
>> >
>> > Allow to disable ioport intercept by userspace.
>> >
>> > Cc: Paolo Bonzini <pbonzini@redhat.com>
>> > Cc: Radim Krčmář <rkrcmar@redhat.com>
>> > Cc: Tim Shearer <tshearer@advaoptical.com>
>> > Cc: Liran Alon <liran.alon@oracle.com>
>> > Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
>> > ---
>> > Documentation/virtual/kvm/api.txt | 11 +++++++++++
>> > arch/x86/include/asm/kvm_host.h | 2 ++
>> > arch/x86/kvm/x86.c | 5 +++++
>> > include/uapi/linux/kvm.h | 1 +
>> > 4 files changed, 19 insertions(+)
>> >
>> > diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
>> > index 1c7958b..3d0488e 100644
>> > --- a/Documentation/virtual/kvm/api.txt
>> > +++ b/Documentation/virtual/kvm/api.txt
>> > @@ -4378,6 +4378,17 @@ all such vmexits.
>> >
>> > Do not enable KVM_FEATURE_PV_UNHALT if you disable HLT exits.
>> >
>> > +7.14 KVM_CAP_IOPORT_DISABLE_INTERCEPT
>> > +
>> > +Architectures: x86
>
> And to be exact: Intel only..
next prev parent reply other threads:[~2018-05-15 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 5:45 [PATCH 0/3] KVM: VMX: Allow to disable ioport intercept per-VM by userspace Wanpeng Li
2018-04-17 5:46 ` [PATCH 1/3] KVM: VMX: Introduce per-VM I/O permission bitmaps Wanpeng Li
2018-05-11 15:39 ` Konrad Rzeszutek Wilk
2018-05-15 21:55 ` Jim Mattson
2018-04-17 5:46 ` [PATCH 2/3] KVM: X86: Allow userspace to disable ioport intercept Wanpeng Li
2018-05-11 15:42 ` Konrad Rzeszutek Wilk
2018-05-11 15:43 ` Konrad Rzeszutek Wilk
2018-05-15 21:56 ` Jim Mattson [this message]
2018-05-16 1:13 ` Wanpeng Li
2018-04-17 5:46 ` [PATCH 3/3] KVM: VMX: Allow I/O port 0x80 bypass when userspace prefer Wanpeng Li
2018-05-11 15:44 ` Konrad Rzeszutek Wilk
2018-05-15 21:57 ` Jim Mattson
2018-05-08 7:55 ` [PATCH 0/3] KVM: VMX: Allow to disable ioport intercept per-VM by userspace Wanpeng Li
2018-05-08 16:14 ` Paolo Bonzini
2018-05-11 15:40 ` Konrad Rzeszutek Wilk
2018-05-12 1:03 ` Wanpeng Li
2018-05-14 13:48 ` Tim Shearer
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=CALMp9eT5aD0tjdTzTABo5a0aEtB52bZ7_-PCTF35Tikf8Q-vDg@mail.gmail.com \
--to=jmattson@google.com \
--cc=kernellwp@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tshearer@advaoptical.com \
--subject='Re: [PATCH 2/3] KVM: X86: Allow userspace to disable ioport intercept' \
/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
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).