From: Nicolin Chen <nicolinc@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: <alex.williamson@redhat.com>, <jgg@nvidia.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 5/5] iommufd/selftest: Add coverage for reporting max_pasid_log2 via IOMMU_HW_INFO
Date: Fri, 21 Mar 2025 13:29:21 -0700 [thread overview]
Message-ID: <Z93MIWxPutO4FDP6@Asurada-Nvidia> (raw)
In-Reply-To: <20250321180143.8468-6-yi.l.liu@intel.com>
On Fri, Mar 21, 2025 at 11:01:43AM -0700, Yi Liu wrote:
> IOMMU_HW_INFO is extended to report max_pasid_log2, hence add coverage
> for it.
>
> Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
> Signed-off-by: Yi Liu <yi.l.liu@intel.com>
It seems that I was CCed only in two patches of this v9. So, I
have to reply to this one.
For the whole series,
Tested-by: Nicolin Chen <nicolinc@nvidia.com>
With an integration of Yi's QEMU patches, I am able to detect
the PASID cap to run vSVA cases in a VM enabling vSMMU.
Selftest also runs correctly.
Thanks
Nicolin
next prev parent reply other threads:[~2025-03-21 20:29 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 [this message]
2025-03-25 13:25 ` [PATCH v9 0/5] vfio-pci support pasid attach/detach 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=Z93MIWxPutO4FDP6@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=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=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