| commit | 5485298ce0978458839a9a7f0f227f7ed64a025f | |
| author | Avihai Horon <avihaih@nvidia.com> | |
| Wed, 2 Aug 2023 08:14:44 +0000 (2 11:14 +0300) | ||
| committer | Cédric Le Goater <clg@redhat.com> | |
| Mon, 11 Sep 2023 06:34:05 +0000 (11 08:34 +0200) | ||
| tree | 4b5e62e28e436c900820791a3a068c1153ba6685 | treesnapshot (tar.gz zip) |
| parent | c5ea91da443b458352c1b629b490ee6631775cb4 | commitdiff |
vfio/migration: Move from STOP_COPY to STOP in vfio_save_cleanup()
Changing the device state from STOP_COPY to STOP can take time as the
device may need to free resources and do other operations as part of the
transition. Currently, this is done in vfio_save_complete_precopy() and
therefore it is counted in the migration downtime.
To avoid this, change the device state from STOP_COPY to STOP in
vfio_save_cleanup(), which is called after migration has completed and
thus is not part of migration downtime.
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Tested-by: YangHang Liu <yanghliu@redhat.com>
Signed-off-by: Cédric Le Goater <clg@redhat.com>
Changing the device state from STOP_COPY to STOP can take time as the
device may need to free resources and do other operations as part of the
transition. Currently, this is done in vfio_save_complete_precopy() and
therefore it is counted in the migration downtime.
To avoid this, change the device state from STOP_COPY to STOP in
vfio_save_cleanup(), which is called after migration has completed and
thus is not part of migration downtime.
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Tested-by: YangHang Liu <yanghliu@redhat.com>
Signed-off-by: Cédric Le Goater <clg@redhat.com>
| hw/vfio/migration.c | diffblobblamehistory |