diff options
| author | Kirti Wankhede <kwankhede@nvidia.com> | 2021-06-09 00:07:21 +0530 |
|---|---|---|
| committer | Alex Williamson <alex.williamson@redhat.com> | 2021-06-18 09:10:35 -0600 |
| commit | d742d064c1f541ac8ad6541e248a97f2dc502721 (patch) | |
| tree | cb2ca8b424f9ff3f1c6bed536aeb66028ca4d613 /semihosting/config.c | |
| parent | 22fca190e25b10761925bb1eeadeda07aabf3c26 (diff) | |
| download | qemu-d742d064c1f541ac8ad6541e248a97f2dc502721.zip qemu-d742d064c1f541ac8ad6541e248a97f2dc502721.tar.gz qemu-d742d064c1f541ac8ad6541e248a97f2dc502721.tar.bz2 | |
vfio/migration: Correct device state from vmstate change for savevm case
Set _SAVING flag for device state from vmstate change handler when it
gets called from savevm.
Currently State transition savevm/suspend is seen as:
_RUNNING -> _STOP -> Stop-and-copy -> _STOP
State transition savevm/suspend should be:
_RUNNING -> Stop-and-copy -> _STOP
State transition from _RUNNING to _STOP occurs from
vfio_vmstate_change() where when vmstate changes from running to
!running, _RUNNING flag is reset but at the same time when
vfio_vmstate_change() is called for RUN_STATE_SAVE_VM, _SAVING bit
should be set.
Reported by: Yishai Hadas <yishaih@nvidia.com>
Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>
Message-Id: <1623177441-27496-1-git-send-email-kwankhede@nvidia.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'semihosting/config.c')
0 files changed, 0 insertions, 0 deletions