From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 00/11] VFIO updates 2016-05-26
Date: Thu, 26 May 2016 12:00:32 -0600 [thread overview]
Message-ID: <20160526175810.13473.82479.stgit@gimli.home> (raw)
The following changes since commit 2c56d06bafd8933d2a9c6e0aeb5d45f7c1fb5616:
Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging (2016-05-26 14:29:30 +0100)
are available in the git repository at:
git://github.com/awilliam/qemu-vfio.git tags/vfio-update-20160526.1
for you to fetch changes up to f1f9365019bb257af087b454972c396bb0d53b26:
vfio: Check that IOMMU MR translates to system address space (2016-05-26 11:12:09 -0600)
----------------------------------------------------------------
VFIO updates 2016-05-26
- Infrastructure and quirks to support IGD assignment (Alex Williamson)
- Fixes to 128bit handling, IOMMU replay, IOMMU translation sanity
checking (Alexey Kardashevskiy)
----------------------------------------------------------------
Alex Williamson (8):
vfio: Enable sparse mmap capability
vfio: Create device specific region info helper
vfio/pci: Fix return of vfio_populate_vga()
vfio/pci: Consolidate VGA setup
vfio/pci: Setup BAR quirks after capabilities probing
vfio/pci: Intel graphics legacy mode assignment
vfio/pci: Add a separate option for IGD OpRegion support
vfio/pci: Add IGD documentation
Alexey Kardashevskiy (3):
vfio: Fix 128 bit handling when deleting region
memory: Fix IOMMU replay base address
vfio: Check that IOMMU MR translates to system address space
docs/igd-assign.txt | 133 +++++++++
hw/ppc/spapr_iommu.c | 2 +-
hw/vfio/common.c | 140 +++++++--
hw/vfio/pci-quirks.c | 643 +++++++++++++++++++++++++++++++++++++++++-
hw/vfio/pci.c | 151 ++++++----
hw/vfio/pci.h | 8 +
include/hw/vfio/vfio-common.h | 3 +
trace-events | 11 +-
8 files changed, 1016 insertions(+), 75 deletions(-)
create mode 100644 docs/igd-assign.txt
next reply other threads:[~2016-05-26 18:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 18:00 Alex Williamson [this message]
2016-05-26 18:00 ` [Qemu-devel] [PULL 01/11] vfio: Enable sparse mmap capability Alex Williamson
2016-05-26 18:00 ` [Qemu-devel] [PULL 02/11] vfio: Create device specific region info helper Alex Williamson
2016-05-26 18:00 ` [Qemu-devel] [PULL 03/11] vfio/pci: Fix return of vfio_populate_vga() Alex Williamson
2016-05-26 18:00 ` [Qemu-devel] [PULL 04/11] vfio/pci: Consolidate VGA setup Alex Williamson
2016-05-26 18:01 ` [Qemu-devel] [PULL 05/11] vfio/pci: Setup BAR quirks after capabilities probing Alex Williamson
2016-05-26 18:01 ` [Qemu-devel] [PULL 06/11] vfio/pci: Intel graphics legacy mode assignment Alex Williamson
2016-05-26 18:01 ` [Qemu-devel] [PULL 07/11] vfio/pci: Add a separate option for IGD OpRegion support Alex Williamson
2016-05-26 18:01 ` [Qemu-devel] [PULL 08/11] vfio/pci: Add IGD documentation Alex Williamson
2016-05-26 18:01 ` [Qemu-devel] [PULL 09/11] vfio: Fix 128 bit handling when deleting region Alex Williamson
2016-05-26 18:01 ` [Qemu-devel] [PULL 10/11] memory: Fix IOMMU replay base address Alex Williamson
2016-05-26 18:01 ` [Qemu-devel] [PULL 11/11] vfio: Check that IOMMU MR translates to system address space Alex Williamson
2016-05-26 19:07 ` [Qemu-devel] [PULL 00/11] VFIO updates 2016-05-26 Peter Maydell
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=20160526175810.13473.82479.stgit@gimli.home \
--to=alex.williamson@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;
as well as URLs for NNTP newsgroup(s).