Joao Martins e46883204c vfio/migration: Block migration with vIOMMU ... Migrating with vIOMMU will require either tracking maximum IOMMU supported address space (e.g. 39/48 address width on Intel) or range-track current mappings and dirty track the new ones post starting dirty tracking. This will be done as a separate series, so add a live migration blocker until that is fixed. Signed-off-by: Joao Martins <joao.m.martins@oracle.com> Reviewed-by: Cédric Le Goater <clg@redhat.com> Link: https://lore.kernel.org/r/20230307125450.62409-14-joao.m.martins@oracle.com Signed-off-by: Alex Williamson <alex.williamson@redhat.com>		2023-03-07 10:21:22 -07:00
..
vfio-amd-xgbe.h	Use DECLARE_*CHECKER* macros	2020-09-09 09:27:09 -04:00
vfio-calxeda-xgmac.h	Use DECLARE_*CHECKER* macros	2020-09-09 09:27:09 -04:00
vfio-common.h	vfio/migration: Block migration with vIOMMU	2023-03-07 10:21:22 -07:00
vfio-platform.h	Use DECLARE_*CHECKER* macros	2020-09-09 09:27:09 -04:00
vfio.h	Clean up header guards that don't match their file name	2016-07-12 16:19:16 +02:00