diff options
author | Avihai Horon <avihaih@nvidia.com> | 2023-06-21 14:12:01 +0300 |
---|---|---|
committer | Cédric Le Goater <clg@redhat.com> | 2023-06-30 06:02:51 +0200 |
commit | 745c42912a04306e8c7765dd4cc1574a92de4446 (patch) | |
tree | 9ee82cef34ab44292802318abe938ca7f4ad0ac9 /hw/s390x | |
parent | eda7362af9595a9c6b1f1fefdd94b5ef711c250c (diff) | |
download | qemu-745c42912a04306e8c7765dd4cc1574a92de4446.zip qemu-745c42912a04306e8c7765dd4cc1574a92de4446.tar.gz qemu-745c42912a04306e8c7765dd4cc1574a92de4446.tar.bz2 |
vfio/migration: Add support for switchover ack capability
Loading of a VFIO device's data can take a substantial amount of time as
the device may need to allocate resources, prepare internal data
structures, etc. This can increase migration downtime, especially for
VFIO devices with a lot of resources.
To solve this, VFIO migration uAPI defines "initial bytes" as part of
its precopy data stream. Initial bytes can be used in various ways to
improve VFIO migration performance. For example, it can be used to
transfer device metadata to pre-allocate resources in the destination.
However, for this to work we need to make sure that all initial bytes
are sent and loaded in the destination before the source VM is stopped.
Use migration switchover ack capability to make sure a VFIO device's
initial bytes are sent and loaded in the destination before the source
stops the VM and attempts to complete the migration.
This can significantly reduce migration downtime for some devices.
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Tested-by: YangHang Liu <yanghliu@redhat.com>
Acked-by: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Cédric Le Goater <clg@redhat.com>
Diffstat (limited to 'hw/s390x')
0 files changed, 0 insertions, 0 deletions