[Intel-gfx] [PATCH v2 00/11] Connect VFIO to IOMMUFD
Yi Liu
yi.l.liu at intel.com
Mon Nov 14 12:51:58 UTC 2022
On 2022/11/10 00:57, Jason Gunthorpe wrote:
> On Tue, Nov 08, 2022 at 11:18:03PM +0800, Yi Liu wrote:
>> On 2022/11/8 17:19, Nicolin Chen wrote:
>>> On Mon, Nov 07, 2022 at 08:52:44PM -0400, Jason Gunthorpe wrote:
>>>
>>>> This is on github: https://github.com/jgunthorpe/linux/commits/vfio_iommufd
>>> [...]
>>>> v2:
>>>> - Rebase to v6.1-rc3, v4 iommufd series
>>>> - Fixup comments and commit messages from list remarks
>>>> - Fix leaking of the iommufd for mdevs
>>>> - New patch to fix vfio modaliases when vfio container is disabled
>>>> - Add a dmesg once when the iommufd provided /dev/vfio/vfio is opened
>>>> to signal that iommufd is providing this
>>>
>>> I've redone my previous sanity tests. Except those reported bugs,
>>> things look fine. Once we fix those issues, GVT and other modules
>>> can run some more stressful tests, I think.
>>
>> our side is also starting test (gvt, nic passthrough) this version. need to
>> wait a while for the result.
>
> I've updated the branches with the two functional fixes discussed on
> the list plus all the doc updates.
>
I see, due to timzone, the kernel we grabbed is 37c9e6e44d77a, it has
slight diff in the scripts/kernel-doc compared with the latest commit
(6bb16a9c67769). I don't think it impacts the test.
https://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git/log/?h=for-next
(37c9e6e44d77a)
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>
--
Regards,
Yi Liu
More information about the Intel-gfx
mailing list