From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/3] VFIO updates 2017-02-10
Date: Fri, 10 Feb 2017 14:42:49 -0700 [thread overview]
Message-ID: <20170210214127.22071.16525.stgit@gimli.home> (raw)
The following changes since commit 98b2faeaee96ab084d0b1669918688d8895c155f:
Merge remote-tracking branch 'remotes/jnsnow/tags/ide-pull-request' into
staging (2017-02-10 18:07:02 +0000)
are available in the git repository at:
git://github.com/awilliam/qemu-vfio.git tags/vfio-updates-20170210.0
for you to fetch changes up to e197de50c6cfad69d2c26c22693b57678ae99d14:
hw/vfio: Add CONFIG switches for calxeda-xgmac and amd-xgbe (2017-02-10
13:12:03 -0700)
----------------------------------------------------------------
VFIO updates 2017-02-10
- Fix GTT wrap-around for Skylake IGD assignment (Alex Williamson)
- Tag vfio-pci-igd-lpc-bridge as bridge device category (Thomas Huth)
- Don't build calxeda-xgmac or amd-xgbe except on ARM (Thomas Huth)
----------------------------------------------------------------
Alex Williamson (1):
vfio-pci: Fix GTT wrap-around for Skylake+ IGD
Thomas Huth (2):
hw/vfio/pci-quirks: Set category of the "vfio-pci-igd-lpc-bridge" device
hw/vfio: Add CONFIG switches for calxeda-xgmac and amd-xgbe
default-configs/arm-softmmu.mak | 2 ++
hw/vfio/Makefile.objs | 4 ++--
hw/vfio/pci-quirks.c | 6 +++++-
3 files changed, 9 insertions(+), 3 deletions(-)
next reply other threads:[~2017-02-10 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 21:42 Alex Williamson [this message]
2017-02-10 21:43 ` [Qemu-devel] [PULL 1/3] vfio-pci: Fix GTT wrap-around for Skylake+ IGD Alex Williamson
2017-02-10 21:43 ` [Qemu-devel] [PULL 2/3] hw/vfio/pci-quirks: Set category of the "vfio-pci-igd-lpc-bridge" device Alex Williamson
2017-02-10 21:43 ` [Qemu-devel] [PULL 3/3] hw/vfio: Add CONFIG switches for calxeda-xgmac and amd-xgbe Alex Williamson
2017-02-13 10:15 ` [Qemu-devel] [PULL 0/3] VFIO updates 2017-02-10 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=20170210214127.22071.16525.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).