diff options
author | Avihai Horon <avihaih@nvidia.com> | 2023-02-16 16:36:23 +0200 |
---|---|---|
committer | Alex Williamson <alex.williamson@redhat.com> | 2023-02-16 12:13:46 -0700 |
commit | 8b942af393a2d9f822aea4e5e0d241e668146bf2 (patch) | |
tree | c0361033c16d18bf865f07fdc4eea57fa72e4d74 /hw/char | |
parent | b051a3f640e2efc95e9e23c5cb1bb5a4c07731e2 (diff) | |
download | qemu-8b942af393a2d9f822aea4e5e0d241e668146bf2.zip qemu-8b942af393a2d9f822aea4e5e0d241e668146bf2.tar.gz qemu-8b942af393a2d9f822aea4e5e0d241e668146bf2.tar.bz2 |
vfio/common: Change vfio_devices_all_running_and_saving() logic to equivalent one
vfio_devices_all_running_and_saving() is used to check if migration is
in pre-copy phase. This is done by checking if migration is in setup or
active states and if all VFIO devices are in pre-copy state, i.e.
_SAVING | _RUNNING.
In VFIO migration protocol v2 pre-copy support is made optional. Hence,
a matching v2 protocol pre-copy state can't be used here.
As preparation for adding v2 protocol, change
vfio_devices_all_running_and_saving() logic such that it doesn't use the
VFIO pre-copy state.
The new equivalent logic checks if migration is in active state and if
all VFIO devices are in running state [1]. No functional changes
intended.
[1] Note that checking if migration is in setup or active states and if
all VFIO devices are in running state doesn't guarantee that we are in
pre-copy phase, thus we check if migration is only in active state.
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Link: https://lore.kernel.org/r/20230216143630.25610-5-avihaih@nvidia.com
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'hw/char')
0 files changed, 0 insertions, 0 deletions