Kernel KVM virtualization development
 help / color / mirror / Atom feed
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 fixes for v4.18-rc4
Date: Fri, 6 Jul 2018 10:48:45 -0600	[thread overview]
Message-ID: <20180706104845.71211867@t450s.home> (raw)

Hi Linus,

The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:

  Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)

are available in the Git repository at:

  git://github.com/awilliam/linux-vfio.git tags/vfio-v4.18-rc4

for you to fetch changes up to d7ef4899d7182f9d4267b4e4a5cc3689c1a04f25:

  sample/vfio-mdev: Change return type to vm_fault_t (2018-07-04 10:42:04 -0600)

----------------------------------------------------------------
VFIO fixes for v4.18

 - Make vfio-pci IGD extensions optional via Kconfig (Alex Williamson)

 - Remove unused and soon to be removed map_atomic callback from mbochs
   sample driver, add unmap callback to avoid dmabuf leaks (Gerd Hoffmann)

 - Fix usage of get_user_pages_longterm() (Jason Gunthorpe)

 - Fix sample mbochs driver vm_operations_struct.fault return type
   (Souptick Joarder)

----------------------------------------------------------------
Alex Williamson (1):
      vfio/pci: Make IGD support a configurable option

Gerd Hoffmann (2):
      sample/mdev/mbochs: remove mbochs_kmap_atomic_dmabuf
      sample/mdev/mbochs: add mbochs_kunmap_dmabuf

Jason Gunthorpe (1):
      vfio: Use get_user_pages_longterm correctly

Souptick Joarder (1):
      sample/vfio-mdev: Change return type to vm_fault_t

 drivers/vfio/pci/Kconfig        | 12 ++++++++++--
 drivers/vfio/vfio_iommu_type1.c | 16 +++++++---------
 samples/vfio-mdev/mbochs.c      | 19 ++++++++-----------
 3 files changed, 25 insertions(+), 22 deletions(-)

                 reply	other threads:[~2018-07-06 16:48 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=20180706104845.71211867@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