From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [GIT PULL] VFIO updates for v4.7-rc1
Date: Wed, 25 May 2016 10:31:48 -0600 [thread overview]
Message-ID: <20160525103148.5995f2a0@ul30vt.home> (raw)
Hi Linus,
The following changes since commit 02da2d72174c61988eb4456b53f405e3ebdebce4:
Linux 4.6-rc5 (2016-04-24 16:17:05 -0700)
are available in the git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v4.7-rc1
for you to fetch changes up to f70552809419cd2abc0cc6469a07c9792a3aaa6c:
vfio_pci: Test for extended capabilities if config space > 256 bytes (2016-05-19 15:04:40 -0600)
----------------------------------------------------------------
VFIO updates for v4.7-rc1
- Hide INTx on certain known broken devices (Alex Williamson)
- Additional backdoor reset detection (Alex Williamson)
- Remove unused iommudata reference (Alexey Kardashevskiy)
- Use cfg_size to avoid probing extended config space (Alexey Kardashevskiy)
----------------------------------------------------------------
Alex Williamson (2):
vfio/pci: Hide broken INTx support from user
vfio/pci: Add test for BAR restore
Alexey Kardashevskiy (2):
vfio_iommu_spapr_tce: Remove unneeded iommu_group_get_iommudata
vfio_pci: Test for extended capabilities if config space > 256 bytes
drivers/vfio/pci/vfio_pci.c | 55 ++++++++++++++++++++++++++++++-------
drivers/vfio/pci/vfio_pci_config.c | 46 +++++++++++++++++++++++++------
drivers/vfio/pci/vfio_pci_private.h | 1 +
drivers/vfio/vfio_iommu_spapr_tce.c | 2 --
4 files changed, 84 insertions(+), 20 deletions(-)
reply other threads:[~2016-05-25 16:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160525103148.5995f2a0@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).