public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: alex.williamson@redhat.com, kevin.tian@intel.com,
	eric.auger@redhat.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 v9 0/5] vfio-pci support pasid attach/detach
Date: Tue, 25 Mar 2025 10:25:21 -0300	[thread overview]
Message-ID: <Z+KuwfSNHnG2DwHr@nvidia.com> (raw)
In-Reply-To: <20250321180143.8468-1-yi.l.liu@intel.com>

On Fri, Mar 21, 2025 at 11:01:38AM -0700, Yi Liu wrote:

> Yi Liu (5):
>   ida: Add ida_find_first_range()
>   vfio-iommufd: Support pasid [at|de]tach for physical VFIO devices
>   vfio: VFIO_DEVICE_[AT|DE]TACH_IOMMUFD_PT support pasid
>   iommufd: Extend IOMMU_GET_HW_INFO to report PASID capability
>   iommufd/selftest: Add coverage for reporting max_pasid_log2 via
>     IOMMU_HW_INFO

Applied to iommufd for-next, thanks

Jason

      parent reply	other threads:[~2025-03-25 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21 18:01 [PATCH v9 0/5] vfio-pci support pasid attach/detach Yi Liu
2025-03-21 18:01 ` [PATCH v9 1/5] ida: Add ida_find_first_range() Yi Liu
2025-03-21 18:01 ` [PATCH v9 2/5] vfio-iommufd: Support pasid [at|de]tach for physical VFIO devices Yi Liu
2025-03-21 18:01 ` [PATCH v9 3/5] vfio: VFIO_DEVICE_[AT|DE]TACH_IOMMUFD_PT support pasid Yi Liu
2025-03-21 18:01 ` [PATCH v9 4/5] iommufd: Extend IOMMU_GET_HW_INFO to report PASID capability Yi Liu
2025-03-21 18:01 ` [PATCH v9 5/5] iommufd/selftest: Add coverage for reporting max_pasid_log2 via IOMMU_HW_INFO Yi Liu
2025-03-21 20:29   ` Nicolin Chen
2025-03-25 13:25 ` Jason Gunthorpe [this message]

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=Z+KuwfSNHnG2DwHr@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=eric.auger@redhat.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --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