Re: [PATCH v3 00/11] Connect VFIO to IOMMUFD

[Jason Gunthorpe <jgg@nvidia.com>]

On Wed, Nov 23, 2022 at 10:44:12AM +0800, Yi Liu wrote:
> Hi Jason,
> 
> On 2022/11/17 05:05, Jason Gunthorpe wrote:
> > This series provides an alternative container layer for VFIO implemented
> > using iommufd. This is optional, if CONFIG_IOMMUFD is not set then it will
> > not be compiled in.
> > 
> > At this point iommufd can be injected by passing in a iommfd FD to
> > VFIO_GROUP_SET_CONTAINER which will use the VFIO compat layer in iommufd
> > to obtain the compat IOAS and then connect up all the VFIO drivers as
> > appropriate.
> > 
> > This is temporary stopping point, a following series will provide a way to
> > directly open a VFIO device FD and directly connect it to IOMMUFD using
> > native ioctls that can expose the IOMMUFD features like hwpt, future
> > vPASID and dynamic attachment.
> > 
> > This series, in compat mode, has passed all the qemu tests we have
> > available, including the test suites for the Intel GVT mdev. Aside from
> > the temporary limitation with P2P memory this is belived to be fully
> > compatible with VFIO.
> > 
> > This is on github: https://github.com/jgunthorpe/linux/commits/vfio_iommufd
> > 
> > It requires the iommufd series:
> > 
> > https://lore.kernel.org/r/0-v5-4001c2997bd0+30c-iommufd_jgg@nvidia.com
> 
> gvtg test encountered broken display with below commit in your for-next
> branch.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git/commit/?h=for-next&id=57f62422b6f0477afaddd2fc77a4bb9b94275f42
> 
> I noticed there are diffs in drivers/vfio/ and drivers/iommu/iommufd/
> between this commit and the last tested commit (37c9e6e44d77a). Seems
> to have regression due to the diffs.

Do you have something more to go on? I am checking the diff and not
getting any idea. The above also merges v6.1-rc5 into the tree, is
there a chance rc5 is the gvt problem?

Jason