LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
"Tim Shearer" <tshearer@advaoptical.com>,
"Liran Alon" <liran.alon@oracle.com>
Subject: Re: [PATCH 0/3] KVM: VMX: Allow to disable ioport intercept per-VM by userspace
Date: Tue, 8 May 2018 18:14:07 +0200 [thread overview]
Message-ID: <c41802dd-8c45-ae00-9b14-b5a04e964f7c@redhat.com> (raw)
In-Reply-To: <CANRm+CzEdE2xMWju56g8jPVAHQ7BTue_=CV+zP6_46dpfb3Kgg@mail.gmail.com>
On 08/05/2018 09:55, Wanpeng Li wrote:
> 2018-04-17 13:45 GMT+08:00 Wanpeng Li <kernellwp@gmail.com>:
>> Tim Shearer reported that "There is a guest which is running a packet
>> forwarding app based on the DPDK (dpdk.org). The packet receive routine
>> writes to 0xc070 using glibc's "outw_p" function which does an additional
>> write to I/O port 0x80. It does this write for every packet that's
>> received, causing a flood of KVM userspace context switches". He uses
>> mpstat to observe a CPU performing L2 packet forwarding on a pinned
>> guest vCPU, the guest time is 95 percent when allowing I/O port 0x80
>> bypass, however, it is 65.78 percent when I/O port 0x80 bypss is
>> disabled.
>>
>> This patchset introduces per-VM I/O permission bitmaps, the userspace
>> can disable the ioport intercept when they are more concern the
>> performance than the security.
>>
>> 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>
>>
>
> Hi Paolo,
>
> Did you send the patch to glibc or the patchset still can be considered?
I haven't, but I'm still not sure about the usefulness of these patches.
Paolo
>
> Regards,
> Wanpeng Li
>
>> Wanpeng Li (3):
>> KVM: VMX: Introduce per-VM I/O permission bitmaps
>> KVM: X86: Allow userspace to disable ioport intercept
>> KVM: VMX: Allow I/O port 0x80 bypass when userspace prefer
>>
>> Documentation/virtual/kvm/api.txt | 11 +++++++++++
>> arch/x86/include/asm/kvm_host.h | 2 ++
>> arch/x86/kvm/vmx.c | 41 ++++++++++++++++++++++++++++++++++++---
>> arch/x86/kvm/x86.c | 5 +++++
>> include/uapi/linux/kvm.h | 1 +
>> 5 files changed, 57 insertions(+), 3 deletions(-)
>>
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2018-05-08 16:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 5:45 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
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 [this message]
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=c41802dd-8c45-ae00-9b14-b5a04e964f7c@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=rkrcmar@redhat.com \
--cc=tshearer@advaoptical.com \
--subject='Re: [PATCH 0/3] KVM: VMX: Allow to disable ioport intercept per-VM by userspace' \
/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).