aboutsummaryrefslogtreecommitdiff
path: root/hw/display/meson.build
diff options
context:
space:
mode:
authorZhenzhong Duan <zhenzhong.duan@intel.com>2023-11-21 16:44:13 +0800
committerCédric Le Goater <clg@redhat.com>2023-12-19 19:03:38 +0100
commit336f308958d598f3db351bb7d94cc57b4b2d448d (patch)
tree649cc76d5bac75dd040834fdfe1cb0345a0300e0 /hw/display/meson.build
parent3016e60f8f715d2058a48e4956be994482c5e218 (diff)
vfio/ap: Allow the selection of a given iommu backend
Now we support two types of iommu backends, let's add the capability to select one of them. This depends on whether an iommufd object has been linked with the vfio-ap device: if the user wants to use the legacy backend, it shall not link the vfio-ap device with any iommufd object: -device vfio-ap,sysfsdev=/sys/bus/mdev/devices/XXX This is called the legacy mode/backend. If the user wants to use the iommufd backend (/dev/iommu) it shall pass an iommufd object id in the vfio-ap device options: -object iommufd,id=iommufd0 -device vfio-ap,sysfsdev=/sys/bus/mdev/devices/XXX,iommufd=iommufd0 Suggested-by: Alex Williamson <alex.williamson@redhat.com> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com> Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com> Reviewed-by: Cédric Le Goater <clg@redhat.com> Tested-by: Nicolin Chen <nicolinc@nvidia.com> Signed-off-by: Cédric Le Goater <clg@redhat.com>
Diffstat (limited to 'hw/display/meson.build')
0 files changed, 0 insertions, 0 deletions