[PATCH v2 00/11] Connect VFIO to IOMMUFD

Yi Liu yi.l.liu at intel.com
Mon Nov 14 14:42:06 UTC 2022


On 2022/11/14 22:38, Jason Gunthorpe wrote:
> On Mon, Nov 14, 2022 at 08:51:58PM +0800, Yi Liu wrote:
> 
>> Our side, Yu He, Lixiao Yang has done below tests on Intel platform with
>> the above kernel, results are:
>>
>> 1) GVT-g test suit passed, Intel iGFx passthrough passed.
>>
>> 2) NIC passthrough test with different guest memory (1G/4G), passed.
>>
>> 3) Booting two different QEMUs in the same time but one QEMU opens
>> legacy /dev/vfio/vfio and another opens /dev/iommu. Tests passed.
>>
>> 4) Tried below Kconfig combinations, results are expected.
>>
>> VFIO_CONTAINER=y, IOMMUFD=y   -- test pass
>> VFIO_CONTAINER=y, IOMMUFD=n   -- test pass
>> VFIO_CONTAINER=n, IOMMUFD=y , IOMMUFD_VFIO_CONTAINER=y  -- test pass
>> VFIO_CONTAINER=n, IOMMUFD=y , IOMMUFD_VFIO_CONTAINER=n  -- no
>> /dev/vfio/vfio, so test fail, expected
>>
>> 5) Tested devices from multi-device group. Assign such devices to the same
>> VM, pass; assign them to different VMs, fail; assign them to a VM with Intel
>> virtual VT-d, fail; Results are expected.
>>
>> Meanwhile, I also tested the branch in development branch for nesting,
>> the basic functionality looks good.
>>
>> Tested-by: Yi Liu <yi.l.liu at intel.com>
> 
> Great thanks!

you are welcome. this is a team work. :)

> In future I also recommend running tests with the CONFIG_IOMMUFD_TEST
> turned on, it enables a bunch more fast path assertions that might
> catch something interesting

oh, sure. will try.

-- 
Regards,
Yi Liu


More information about the dri-devel mailing list