From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: gleb@kernel.org, pbonzini@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, cornelia.huck@de.ibm.com
Subject: Re: [PATCH V4 0/4] Fast MMIO eventfd fixes
Date: Fri, 11 Sep 2015 11:15:30 +0300 [thread overview]
Message-ID: <20150911111453-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1441941457-23630-1-git-send-email-jasowang@redhat.com>
On Fri, Sep 11, 2015 at 11:17:33AM +0800, Jason Wang wrote:
> Hi:
>
> This series fixes two issues of fast mmio eventfd:
>
> 1) A single iodev instance were registerd on two buses: KVM_MMIO_BUS
> and KVM_FAST_MMIO_BUS. This will cause double in
> ioeventfd_destructor()
> 2) A zero length iodev on KVM_MMIO_BUS will never be found but
> kvm_io_bus_cmp(). This will lead e.g the eventfd will be trapped by
> qemu instead of host.
>
> 1 is fixed by allocating two instances of iodev. 2 is fixed by ignore
> the actual length if the length of iodev is zero in kvm_io_bus_cmp().
>
> Please review.
I think we should add a capability for fast mmio.
This way, userspace can avoid crashing buggy kernels.
> Changes from V3:
>
> - Don't do search on two buses when trying to do write on
> KVM_MMIO_BUS. This fixes a small regression found by vmexit.flat.
> - Since we don't do search on two buses, change kvm_io_bus_cmp() to
> let it can find zero length iodevs.
> - Fix the unnecessary lines in tracepoint patch.
>
> Changes from V2:
> - Tweak styles and comment suggested by Cornelia.
>
> Changes from v1:
> - change ioeventfd_bus_from_flags() to return KVM_FAST_MMIO_BUS when
> needed to save lots of unnecessary changes.
>
> Jason Wang (4):
> kvm: factor out core eventfd assign/deassign logic
> kvm: fix double free for fast mmio eventfd
> kvm: fix zero length mmio searching
> kvm: add tracepoint for fast mmio
>
> arch/x86/kvm/trace.h | 18 ++++++++
> arch/x86/kvm/vmx.c | 1 +
> arch/x86/kvm/x86.c | 1 +
> virt/kvm/eventfd.c | 124 ++++++++++++++++++++++++++++++---------------------
> virt/kvm/kvm_main.c | 4 +-
> 5 files changed, 96 insertions(+), 52 deletions(-)
>
> --
> 2.1.4
next prev parent reply other threads:[~2015-09-11 8:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 3:17 [PATCH V4 0/4] Fast MMIO eventfd fixes Jason Wang
2015-09-11 3:17 ` [PATCH V4 1/4] kvm: factor out core eventfd assign/deassign logic Jason Wang
2015-09-11 7:39 ` Cornelia Huck
2015-09-11 8:17 ` Paolo Bonzini
2015-09-11 9:14 ` Jason Wang
2015-09-11 3:17 ` [PATCH V4 2/4] kvm: fix double free for fast mmio eventfd Jason Wang
2015-09-11 7:46 ` Cornelia Huck
2015-09-11 9:25 ` Jason Wang
2015-09-11 10:19 ` Cornelia Huck
2015-09-11 3:17 ` [PATCH V4 3/4] kvm: fix zero length mmio searching Jason Wang
2015-09-11 8:26 ` Paolo Bonzini
2015-09-11 8:31 ` Cornelia Huck
2015-09-11 9:26 ` Jason Wang
2015-09-11 3:17 ` [PATCH V4 4/4] kvm: add tracepoint for fast mmio Jason Wang
2015-09-11 8:15 ` Michael S. Tsirkin [this message]
2015-09-11 8:33 ` [PATCH V4 0/4] Fast MMIO eventfd fixes Paolo Bonzini
2015-09-11 9:28 ` Jason Wang
2015-09-13 8:51 ` Michael S. Tsirkin
2015-09-13 8:52 ` Michael S. Tsirkin
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=20150911111453-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=gleb@kernel.org \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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).