Re: [PATCH v6 5/5] iommufd/selftest: Add coverage for reporting max_pasid_log2 via IOMMU_HW_INFO

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2025/1/15 16:16, Tian, Kevin wrote:
From: Liu, Yi L <yi.l.liu@xxxxxxxxx>
Sent: Thursday, December 19, 2024 9:36 PM

@@ -762,6 +773,13 @@ TEST_F(iommufd_ioas, get_hw_info)
  		 * the fields within the size range still gets updated.
  		 */
  		test_cmd_get_hw_info(self->device_id, &buffer_smaller,
sizeof(buffer_smaller));
+		test_cmd_get_hw_info_pasid(self->device_id, &max_pasid);
+		ASSERT_EQ(0, max_pasid);
+		if (variant->pasid_capable) {
+			test_cmd_get_hw_info_pasid(self->pasid_device_id,
+						   &max_pasid);
+			ASSERT_EQ(20, max_pasid);
+		}

I didn't' find where in the mock iommu sets max_pasid to 20. Does it
rely on another patch or did I overlook here?

yes, it is added in another thread.

https://lore.kernel.org/linux-iommu/20241219132746.16193-1-yi.l.liu@xxxxxxxxx/

--
Regards,
Yi Liu




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux