From: Peter Xu <pet...@redhat.com> Move it one layer down, so taking VFIO-migration as a feature for migration.
Cc: Alex Williamson <alex.william...@redhat.com> Cc: Cédric Le Goater <c...@redhat.com> Reviewed-by: Cédric Le Goater <c...@redhat.com> Link: https://lore.kernel.org/r/20240109064628.595453-10-pet...@redhat.com Signed-off-by: Peter Xu <pet...@redhat.com> --- docs/devel/migration/features.rst | 1 + docs/devel/migration/index.rst | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/devel/migration/features.rst b/docs/devel/migration/features.rst index e257d0d100..dea016f707 100644 --- a/docs/devel/migration/features.rst +++ b/docs/devel/migration/features.rst @@ -8,3 +8,4 @@ Migration has plenty of features to support different use cases. postcopy dirty-limit + vfio diff --git a/docs/devel/migration/index.rst b/docs/devel/migration/index.rst index 21ad58b189..b1357309e1 100644 --- a/docs/devel/migration/index.rst +++ b/docs/devel/migration/index.rst @@ -10,6 +10,5 @@ QEMU live migration works. main features compatibility - vfio virtio best-practices -- 2.43.0
