From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [GIT PULL] VFIO updates for v4.17
Date: Fri, 6 Apr 2018 15:33:22 -0600 [thread overview]
Message-ID: <20180406153322.28e85a8e@t450s.home> (raw)
Hi Linus,
The following changes since commit c698ca5278934c0ae32297a8725ced2e27585d7f:
Linux 4.16-rc6 (2018-03-18 17:48:42 -0700)
are available in the Git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v4.17-rc1
for you to fetch changes up to da9147140fe3de5a3a3fe5fe7f69739d4f39bea1:
MAINTAINERS: vfio/platform: Update sub-maintainer (2018-04-02 09:04:08 -0600)
----------------------------------------------------------------
VFIO updates for v4.17-rc1
- Adopt iommu_unmap_fast() interface to type1 backend
(Suravee Suthikulpanit)
- mdev sample driver fixup (Shunyong Yang)
- More efficient PFN mapping handling in type1 backend
(Jason Cai)
- VFIO device ioeventfd interface (Alex Williamson)
- Tag new vfio-platform sub-maintainer (Alex Williamson)
----------------------------------------------------------------
Alex Williamson (4):
vfio/pci: Pull BAR mapping setup from read-write path
vfio/pci: Use endian neutral helpers
vfio/pci: Add ioeventfd support
MAINTAINERS: vfio/platform: Update sub-maintainer
Jason Cai (Xiang Feng) (1):
vfio/type1: Improve memory pinning process for raw PFN mapping
Shunyong Yang (1):
vfio-mdev/samples: change RDI interrupt condition
Suravee Suthikulpanit (1):
vfio/type1: Adopt fast IOTLB flush interface when unmap IOVAs
MAINTAINERS | 2 +-
drivers/vfio/pci/vfio_pci.c | 35 +++++++
drivers/vfio/pci/vfio_pci_private.h | 19 ++++
drivers/vfio/pci/vfio_pci_rdwr.c | 184 ++++++++++++++++++++++++++++++++----
drivers/vfio/vfio_iommu_type1.c | 151 +++++++++++++++++++++++++----
include/uapi/linux/vfio.h | 27 ++++++
samples/vfio-mdev/mtty.c | 2 +-
7 files changed, 377 insertions(+), 43 deletions(-)
reply other threads:[~2018-04-06 21:33 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=20180406153322.28e85a8e@t450s.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).