From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>
Subject: [GIT PULL] VFIO updates for 3.18-rc1
Date: Sat, 11 Oct 2014 01:56:18 -0600 [thread overview]
Message-ID: <1413014178.4202.15.camel@ul30vt.home> (raw)
Hi Linus,
The following changes since commit fe82dcec644244676d55a1384c958d5f67979adb:
Linux 3.17-rc7 (2014-09-28 14:29:07 -0700)
are available in the git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v3.18-rc1
for you to fetch changes up to 93899a679fd6b2534b5c297d9316bae039ebcbe1:
vfio-pci: Fix remove path locking (2014-09-29 17:18:39 -0600)
----------------------------------------------------------------
VFIO updates for v3.18-rc1
- Nested IOMMU extension to type1 (Will Deacon)
- Restore MSIx message before enabling (Gavin Shan)
- Fix remove path locking (Alex Williamson)
----------------------------------------------------------------
Alex Williamson (1):
vfio-pci: Fix remove path locking
Gavin Shan (3):
PCI: Export MSI message relevant functions
vfio/pci: Restore MSIx message prior to enabling
drivers/vfio: Export vfio_spapr_iommu_eeh_ioctl() with GPL
Will Deacon (2):
iommu: introduce domain attribute for nesting IOMMUs
vfio/iommu_type1: add new VFIO_TYPE1_NESTING_IOMMU IOMMU type
drivers/pci/msi.c | 2 +
drivers/vfio/pci/vfio_pci.c | 136 ++++++++++++++++----------------------
drivers/vfio/pci/vfio_pci_intrs.c | 15 +++++
drivers/vfio/vfio_iommu_type1.c | 30 +++++++--
drivers/vfio/vfio_spapr_eeh.c | 2 +-
include/linux/iommu.h | 1 +
include/uapi/linux/vfio.h | 3 +
7 files changed, 104 insertions(+), 85 deletions(-)
reply other threads:[~2014-10-11 7:56 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=1413014178.4202.15.camel@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