diff options
| author | Zhenzhong Duan <zhenzhong.duan@intel.com> | 2023-11-21 16:44:11 +0800 |
|---|---|---|
| committer | Cédric Le Goater <clg@redhat.com> | 2023-12-19 19:03:38 +0100 |
| commit | a6c50e1c3f8d0eb77edaea392e61508bb3c516f8 (patch) | |
| tree | 9665b05cd63ba1f67e7f6f3ffc3b74302d95b812 /python | |
| parent | da3e04b26fd8d15b344944504d5ffa9c5f20b54b (diff) | |
| download | qemu-a6c50e1c3f8d0eb77edaea392e61508bb3c516f8.zip qemu-a6c50e1c3f8d0eb77edaea392e61508bb3c516f8.tar.gz qemu-a6c50e1c3f8d0eb77edaea392e61508bb3c516f8.tar.bz2 | |
vfio/platform: 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-platform device:
If the user wants to use the legacy backend, it shall not
link the vfio-platform device with any iommufd object:
-device vfio-platform,host=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-platform device options:
-object iommufd,id=iommufd0
-device vfio-platform,host=XXX,iommufd=iommufd0
Suggested-by: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Nicolin Chen <nicolinc@nvidia.com>
Signed-off-by: Cédric Le Goater <clg@redhat.com>
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions