diff options
| author | Joao Martins <joao.m.martins@oracle.com> | 2023-03-07 12:54:48 +0000 |
|---|---|---|
| committer | Alex Williamson <alex.williamson@redhat.com> | 2023-03-07 10:21:22 -0700 |
| commit | e46883204c384f992088f8c3ea713f7e1c2d5a6d (patch) | |
| tree | e88ee1d09482d9107bdc21960013aa93fa04735d /hw/vfio/migration.c | |
| parent | b153402a8941c2193e91ac50ed9720c7da6ee8db (diff) | |
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>
Diffstat (limited to 'hw/vfio/migration.c')
| -rw-r--r-- | hw/vfio/migration.c | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/hw/vfio/migration.c b/hw/vfio/migration.c index a2c3d9bade..776fd2d7cd 100644 --- a/hw/vfio/migration.c +++ b/hw/vfio/migration.c @@ -634,6 +634,11 @@ int vfio_migration_probe(VFIODevice *vbasedev, Error **errp) return ret; } + ret = vfio_block_giommu_migration(errp); + if (ret) { + return ret; + } + trace_vfio_migration_probe(vbasedev->name); return 0; |