All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: eric.auger@redhat.com, peterx@redhat.com, kvm@vger.kernel.org
Subject: [PATCH v2 0/4] vfio/quirks: ioeventfd support
Date: Tue, 01 May 2018 10:42:47 -0600	[thread overview]
Message-ID: <20180501162901.28940.1075.stgit@gimli.home> (raw)

Now that vfio ioeventfd support is in v4.17-rc kernels, let's push
forward with this series.  I've posted the linux-headers update
separate as it was rather an ordeal with conflicting defines, non-
upstream defines, and inveted types that don't exist.  Dependencies
to build this series:

https://lists.gnu.org/archive/html/qemu-devel/2018-05/msg00097.html

Which depends on MST's:

https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg02510.html

The first two patches are unchanged and I've kept previous reviews.
The change to the latter two patches is the addition of trace events
and options for disabling both vfio and KVM ioeventfds.  These are
both experimental options which are useful for debugging and
evaluating any performance differences, not intended for support.
Please review.  Thanks,

Alex

---

Alex Williamson (4):
      vfio/quirks: Add common quirk alloc helper
      vfio/quirks: Add quirk reset callback
      vfio/quirks: ioeventfd quirk acceleration
      vfio/quirks: Enable ioeventfd quirks to be handled by vfio directly


 hw/vfio/pci-quirks.c |  273 +++++++++++++++++++++++++++++++++++++++++++++-----
 hw/vfio/pci.c        |    6 +
 hw/vfio/pci.h        |   19 +++
 hw/vfio/trace-events |    3 +
 4 files changed, 272 insertions(+), 29 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, eric.auger@redhat.com, peterx@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/4] vfio/quirks: ioeventfd support
Date: Tue, 01 May 2018 10:42:47 -0600	[thread overview]
Message-ID: <20180501162901.28940.1075.stgit@gimli.home> (raw)

Now that vfio ioeventfd support is in v4.17-rc kernels, let's push
forward with this series.  I've posted the linux-headers update
separate as it was rather an ordeal with conflicting defines, non-
upstream defines, and inveted types that don't exist.  Dependencies
to build this series:

https://lists.gnu.org/archive/html/qemu-devel/2018-05/msg00097.html

Which depends on MST's:

https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg02510.html

The first two patches are unchanged and I've kept previous reviews.
The change to the latter two patches is the addition of trace events
and options for disabling both vfio and KVM ioeventfds.  These are
both experimental options which are useful for debugging and
evaluating any performance differences, not intended for support.
Please review.  Thanks,

Alex

---

Alex Williamson (4):
      vfio/quirks: Add common quirk alloc helper
      vfio/quirks: Add quirk reset callback
      vfio/quirks: ioeventfd quirk acceleration
      vfio/quirks: Enable ioeventfd quirks to be handled by vfio directly


 hw/vfio/pci-quirks.c |  273 +++++++++++++++++++++++++++++++++++++++++++++-----
 hw/vfio/pci.c        |    6 +
 hw/vfio/pci.h        |   19 +++
 hw/vfio/trace-events |    3 +
 4 files changed, 272 insertions(+), 29 deletions(-)

             reply	other threads:[~2018-05-01 16:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 16:42 Alex Williamson [this message]
2018-05-01 16:42 ` [Qemu-devel] [PATCH v2 0/4] vfio/quirks: ioeventfd support Alex Williamson
2018-05-01 16:43 ` [PATCH v2 1/4] vfio/quirks: Add common quirk alloc helper Alex Williamson
2018-05-01 16:43   ` [Qemu-devel] " Alex Williamson
2018-05-01 16:43 ` [PATCH v2 2/4] vfio/quirks: Add quirk reset callback Alex Williamson
2018-05-01 16:43   ` [Qemu-devel] " Alex Williamson
2018-05-01 16:43 ` [PATCH v2 3/4] vfio/quirks: ioeventfd quirk acceleration Alex Williamson
2018-05-01 16:43   ` [Qemu-devel] " Alex Williamson
2018-05-03  3:36   ` Peter Xu
2018-05-03  3:36     ` [Qemu-devel] " Peter Xu
2018-05-03  4:20     ` Alex Williamson
2018-05-03  4:20       ` [Qemu-devel] " Alex Williamson
2018-05-03 14:33   ` Auger Eric
2018-05-03 14:33     ` [Qemu-devel] " Auger Eric
2018-05-03 14:48     ` Alex Williamson
2018-05-03 14:48       ` [Qemu-devel] " Alex Williamson
2018-05-01 16:43 ` [PATCH v2 4/4] vfio/quirks: Enable ioeventfd quirks to be handled by vfio directly Alex Williamson
2018-05-01 16:43   ` [Qemu-devel] " Alex Williamson
2018-05-03  4:56   ` Peter Xu
2018-05-03  4:56     ` [Qemu-devel] " Peter Xu
2018-05-03 16:29     ` Alex Williamson
2018-05-03 16:29       ` [Qemu-devel] " Alex Williamson
2018-05-04  2:16       ` Peter Xu
2018-05-04  2:16         ` [Qemu-devel] " Peter Xu
2018-05-04  7:38       ` Auger Eric
2018-05-04  7:38         ` [Qemu-devel] " Auger Eric
2018-05-03 15:20   ` Auger Eric
2018-05-03 15:20     ` [Qemu-devel] " Auger Eric
2018-05-03 16:30     ` Alex Williamson
2018-05-03 16:30       ` [Qemu-devel] " Alex Williamson
2018-05-01 16:56 ` [PATCH v2 0/4] vfio/quirks: ioeventfd support no-reply
2018-05-01 16:56   ` [Qemu-devel] " no-reply
2018-05-01 17:05   ` Alex Williamson
2018-05-01 17:05     ` [Qemu-devel] " Alex Williamson
2018-05-01 16:56 ` no-reply
2018-05-01 16:56   ` [Qemu-devel] " no-reply

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=20180501162901.28940.1075.stgit@gimli.home \
    --to=alex.williamson@redhat.com \
    --cc=eric.auger@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.