From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: allen.m.kay@intel.com, kraxel@redhat.com, kvm@vger.kernel.org
Subject: [Qemu-devel] [RFC PATCH v4 0/3] vfio IGD assignment
Date: Fri, 11 Mar 2016 15:59:24 -0700 [thread overview]
Message-ID: <20160311225120.29918.67199.stgit@gimli.home> (raw)
This series applies on top of my latest vfio pull request[1] or
directly to the tag mentioned there[2]. It also requires kernel
support that's currently in linux-next for v4.6, thus the RFC here.
IGD assignment also requires SeaBIOS support as noted in the commit
log of the 3rd patch here. Patch 2 is not directly IGD related, but
it does make use of some of the same features added to the kernel and
is thus queued here as well for review and testing. See patch 3 for a
full description of the level of IGD assignment support offered here.
Please review, test, and comment. Thanks,
Alex
[1] https://lists.nongnu.org/archive/html/qemu-devel/2016-03/msg02743.html
[2] https://github.com/awilliam/qemu-vfio/tree/vfio-update-20160311.0
---
Alex Williamson (3):
linux-headers/vfio: Update matching current linux-next
vfio: Enable sparse mmap capability
vfio/pci: Intel IGD support
hw/vfio/common.c | 67 +++++
hw/vfio/pci-quirks.c | 548 +++++++++++++++++++++++++++++++++++++++++
hw/vfio/pci.c | 68 +++++
hw/vfio/pci.h | 10 +
include/hw/vfio/vfio-common.h | 2
linux-headers/linux/vfio.h | 92 +++++++
trace-events | 9 +
7 files changed, 789 insertions(+), 7 deletions(-)
next reply other threads:[~2016-03-11 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 22:59 Alex Williamson [this message]
2016-03-11 22:59 ` [Qemu-devel] [RFC PATCH v4 1/3] linux-headers/vfio: Update matching current linux-next Alex Williamson
2016-03-11 22:59 ` [Qemu-devel] [RFC PATCH v4 2/3] vfio: Enable sparse mmap capability Alex Williamson
2016-03-11 22:59 ` [Qemu-devel] [RFC PATCH v4 3/3] vfio/pci: Intel IGD support Alex Williamson
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=20160311225120.29918.67199.stgit@gimli.home \
--to=alex.williamson@redhat.com \
--cc=allen.m.kay@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).