diff options
author | Jason Gunthorpe <jgg@nvidia.com> | 2022-11-29 21:39:33 +0100 |
---|---|---|
committer | Jason Gunthorpe <jgg@nvidia.com> | 2022-12-02 16:52:04 +0100 |
commit | 169dd5c987e60e62aa5785b30d22ded2ae000286 (patch) | |
tree | 5e00d30219e9bf021b635c54184ab9381d5e00ac /kernel/trace/fprobe.c | |
parent | vfio/ap: Validate iova during dma_unmap and trigger irq disable (diff) | |
parent | iommufd: Allow iommufd to supply /dev/vfio/vfio (diff) | |
download | linux-169dd5c987e60e62aa5785b30d22ded2ae000286.tar.xz linux-169dd5c987e60e62aa5785b30d22ded2ae000286.zip |
Merge patch series "Connect VFIO to IOMMUFD"
Jason Gunthorpe <jgg@nvidia.com> says:
==================
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-v6-a196d26f289e+11787-iommufd_jgg@nvidia.com
==================
Link: https://lore.kernel.org/r/0-v4-42cd2eb0e3eb+335a-vfio_iommufd_jgg@nvidia.com
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'kernel/trace/fprobe.c')
0 files changed, 0 insertions, 0 deletions