From: Auger Eric <eric.auger@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>, qemu-devel@nongnu.org
Cc: peterx@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 0/5] vfio/quirks: ioeventfd support
Date: Tue, 13 Mar 2018 15:38:21 +0100 [thread overview]
Message-ID: <63020f50-b780-3623-800b-379521e8583a@redhat.com> (raw)
In-Reply-To: <20180228201837.26629.3346.stgit@gimli.home>
Hi Alex,
On 28/02/18 21:45, Alex Williamson wrote:
> This is the QEMU counterpart to https://lkml.org/lkml/2018/2/28/1222
>
> As described in the third patch, we have a use case for taking
> advantage of existing KVM ioeventfd support for accelerating the
> MSI-ACK behavior of NVIDIA GPUs. This series adds generic
> infrastructure within vfio quirks for making use of ioeventfds and
> specifically enables it for this purpose. The first three patches
> provide a performance improvement on their own and do not depend on
> the additional acceleration added by the remainder of the patches to
> be worthwhile. The Linux header update in patch 4 is not intended
> to be a full refresh, the kernel API is not yet upstream, this is for
> testing and review purposes. The intention would be to commit the
> series in separate chunks, 1-3 once we have review consensus, 4-5 as
> RFC until the kernel API is upstream.
>
> RFC->v1:
> * Cap the number of dynamically added ioeventfds to 10 such that
> pathological driver behavior cannot consume too many file handles.
> * Added a reset hook and cleanup mechanism to drop dynamically added
> ioeventfds on device reset.
> * Additional comments and removed info_report.
> * Folded ioeventfd infrastructure patch into usage patch, fail to
> stand on its own without setup, which requires consumers.
>
> Thanks,
>
> Alex
>
> ---
>
> Alex Williamson (5):
> vfio/quirks: Add common quirk alloc helper
> vfio/quirks: Add quirk reset callback
> vfio/quirks: ioeventfd quirk acceleration
> vfio: Update linux header
> vfio/quirks: Enable ioeventfd quirks to be handled by vfio directly
>
>
> hw/vfio/pci-quirks.c | 255 +++++++++++++++++++++++++++++++++++++++-----
> hw/vfio/pci.c | 2
> hw/vfio/pci.h | 17 +++
> linux-headers/linux/vfio.h | 27 +++++
> 4 files changed, 272 insertions(+), 29 deletions(-)
>
For all patches except the yet partial linux header update,
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Thanks
Eric
prev parent reply other threads:[~2018-03-13 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 20:45 [PATCH 0/5] vfio/quirks: ioeventfd support Alex Williamson
2018-02-28 20:45 ` [PATCH 1/5] vfio/quirks: Add common quirk alloc helper Alex Williamson
2018-03-07 7:04 ` Peter Xu
2018-02-28 20:45 ` [PATCH 2/5] vfio/quirks: Add quirk reset callback Alex Williamson
2018-03-07 7:04 ` Peter Xu
2018-02-28 20:45 ` [PATCH 3/5] vfio/quirks: ioeventfd quirk acceleration Alex Williamson
2018-03-07 7:06 ` Peter Xu
2018-02-28 20:46 ` [PATCH 4/5] vfio: Update linux header Alex Williamson
2018-02-28 20:46 ` [PATCH 5/5] vfio/quirks: Enable ioeventfd quirks to be handled by vfio directly Alex Williamson
2018-03-13 14:38 ` Auger Eric [this message]
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=63020f50-b780-3623-800b-379521e8583a@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.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