public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: kevin.tian@intel.com, jgg@nvidia.com, eric.auger@redhat.com,
	nicolinc@nvidia.com, kvm@vger.kernel.org,
	chao.p.peng@linux.intel.com, zhenzhong.duan@intel.com,
	willy@infradead.org, zhangfei.gao@linaro.org,
	vasant.hegde@amd.com
Subject: Re: [PATCH v8 0/5] vfio-pci support pasid attach/detach
Date: Fri, 14 Mar 2025 08:48:13 -0600	[thread overview]
Message-ID: <20250314084813.1a263b66.alex.williamson@redhat.com> (raw)
In-Reply-To: <20250313124753.185090-1-yi.l.liu@intel.com>

On Thu, 13 Mar 2025 05:47:48 -0700
Yi Liu <yi.l.liu@intel.com> wrote:

> This series introduces the PASID attach/detach user APIs (uAPIs) that
> allow userspace to attach or detach a device's PASID to or from a specified
> IOAS/hwpt. Currently, only the vfio-pci driver is enabled in this series.
> 
> Following this update, PASID-capable devices bound to vfio-pci can report
> PASID capabilities to userspace and virtual machines (VMs), facilitating
> PASID use cases such as Shared Virtual Addressing (SVA). In discussions
> about reporting the virtual PASID (vPASID) to VMs [1], it was agreed that
> the userspace virtual machine monitor (VMM) will synthesize the vPASID
> capability. The VMM must identify a suitable location to insert the vPASID
> capability, including handling hidden bits for certain devices. However,
> this responsibility lies with userspace and is not the focus of this series.
> 
> This series begins by adding helpers for PASID attachment in the vfio core,
> then extends the device character device (cdev) attach/detach ioctls to
> support PASID attach/detach operations. At the conclusion of this series,
> the IOMMU_GET_HW_INFO ioctl is extended to report PCI PASID capabilities
> to userspace. Userspace should verify this capability before utilizing any
> PASID-related uAPIs provided by VFIO, as agreed in [2]. This series depends
> on the iommufd PASID attach/detach series [3].
> 
> The complete code is available at [4] and has been tested with a modified
> QEMU branch [5].

What's missing for this to go in and which tree will take it?  At a
glance it seems like 4/ needs a PCI sign-off and 5/ needs an IOMMUFD
sign-off.  Thanks,

Alex


  parent reply	other threads:[~2025-03-14 14:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 12:47 [PATCH v8 0/5] vfio-pci support pasid attach/detach Yi Liu
2025-03-13 12:47 ` [PATCH v8 1/5] ida: Add ida_find_first_range() Yi Liu
2025-03-13 12:47 ` [PATCH v8 2/5] vfio-iommufd: Support pasid [at|de]tach for physical VFIO devices Yi Liu
2025-03-13 12:47 ` [PATCH v8 3/5] vfio: VFIO_DEVICE_[AT|DE]TACH_IOMMUFD_PT support pasid Yi Liu
2025-03-19 17:41   ` Nicolin Chen
2025-03-20 12:37     ` Yi Liu
2025-03-13 12:47 ` [PATCH v8 4/5] iommufd: Extend IOMMU_GET_HW_INFO to report PASID capability Yi Liu
2025-03-17  7:18   ` Yi Liu
2025-03-19 17:58   ` Nicolin Chen
2025-03-20 12:48     ` Yi Liu
2025-03-20 16:47       ` Nicolin Chen
2025-03-20 18:57         ` Jason Gunthorpe
2025-03-20 20:02           ` Nicolin Chen
2025-03-20 23:40             ` Jason Gunthorpe
2025-03-20 23:48               ` Nicolin Chen
2025-03-21  4:27                 ` Nicolin Chen
2025-03-21 17:37                   ` Yi Liu
2025-03-21 18:29                     ` Nicolin Chen
2025-03-21 18:42                       ` Jason Gunthorpe
2025-03-21 19:00                         ` Nicolin Chen
2025-03-13 12:47 ` [PATCH v8 5/5] iommufd/selftest: Add coverage for reporting max_pasid_log2 via IOMMU_HW_INFO Yi Liu
2025-03-19 18:12   ` Nicolin Chen
2025-03-14 14:48 ` Alex Williamson [this message]
2025-03-17  7:25   ` [PATCH v8 0/5] vfio-pci support pasid attach/detach Yi Liu
2025-03-17 19:28     ` Jason Gunthorpe

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=20250314084813.1a263b66.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=eric.auger@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=vasant.hegde@amd.com \
    --cc=willy@infradead.org \
    --cc=yi.l.liu@intel.com \
    --cc=zhangfei.gao@linaro.org \
    --cc=zhenzhong.duan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox