From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>, kvm@vger.kernel.org
Cc: Yi Liu <yi.l.liu@intel.com>
Subject: [GIT PULL vfio] Please pull vfio/iommufd changes
Date: Mon, 3 Apr 2023 13:15:59 -0300 [thread overview]
Message-ID: <ZCr7v8pFz+3rMyAX@nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]
Hi Alex,
Here is the shared branch for the mdev changes
Yi, you should base your series on this commit 7d12578c5d508050554bcd9ca3d2331914d86d71.
Thanks,
Jason
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
//git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git vfio_mdev_ops
for you to fetch changes up to 7d12578c5d508050554bcd9ca3d2331914d86d71:
vfio: Check the presence for iommufd callbacks in __vfio_register_dev() (2023-03-31 13:43:32 -0300)
----------------------------------------------------------------
Nicolin Chen (1):
iommufd: Create access in vfio_iommufd_emulated_bind()
Yi Liu (5):
iommu/iommufd: Pass iommufd_ctx pointer in iommufd_get_ioas()
vfio-iommufd: No need to record iommufd_ctx in vfio_device
vfio-iommufd: Make vfio_iommufd_emulated_bind() return iommufd_access ID
vfio/mdev: Uses the vfio emulated iommufd ops set in the mdev sample drivers
vfio: Check the presence for iommufd callbacks in __vfio_register_dev()
drivers/iommu/iommufd/device.c | 56 +++++++++++++++++++++++++++++++++-----------------------
drivers/iommu/iommufd/ioas.c | 14 +++++++-------
drivers/iommu/iommufd/iommufd_private.h | 4 ++--
drivers/iommu/iommufd/selftest.c | 14 +++++++++-----
drivers/iommu/iommufd/vfio_compat.c | 2 +-
drivers/vfio/iommufd.c | 37 ++++++++++++++++++-------------------
drivers/vfio/vfio_main.c | 5 +++--
include/linux/iommufd.h | 5 +++--
include/linux/vfio.h | 1 -
samples/vfio-mdev/mbochs.c | 3 +++
samples/vfio-mdev/mdpy.c | 3 +++
samples/vfio-mdev/mtty.c | 3 +++
12 files changed, 85 insertions(+), 62 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2023-04-03 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 16:15 Jason Gunthorpe [this message]
2023-04-04 15:22 ` [GIT PULL vfio] Please pull vfio/iommufd changes Liu, Yi L
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=ZCr7v8pFz+3rMyAX@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=yi.l.liu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.