aboutsummaryrefslogtreecommitdiff
path: root/rust/qemu-api-macros/src
diff options
context:
space:
mode:
authorPeter Xu <peterx@redhat.com>2025-01-14 18:07:41 -0500
committerFabiano Rosas <farosas@suse.de>2025-01-29 11:56:41 -0300
commit46b0155ecf3e65ba1497a9eb35e7352c36ed6f31 (patch)
treeaa405b001d2ffb34ac2e3b7a9976bf1398173c74 /rust/qemu-api-macros/src
parenta880ddd8ce387231b9a93fb2964425ea4e6c9728 (diff)
downloadqemu-46b0155ecf3e65ba1497a9eb35e7352c36ed6f31.zip
qemu-46b0155ecf3e65ba1497a9eb35e7352c36ed6f31.tar.gz
qemu-46b0155ecf3e65ba1497a9eb35e7352c36ed6f31.tar.bz2
migration: Notify COMPLETE once for postcopy
Postcopy invokes qemu_savevm_state_complete_precopy() twice, that means it'll invoke COMPLETE notify twice.. also twice the tracepoints that marking precopy complete. Move that notification (along with the tracepoint) out to the caller, so that postcopy will only notify once right at the start of switchover phase from precopy. When at it, rename it to suite the file now it locates. For precopy, there should have no functional change except the tracepoint has a name change. For the other two users of qemu_savevm_state_complete_precopy(), namely: qemu_savevm_state() and qemu_savevm_live_state(): the notifier shouldn't matter because they're not precopy at all. Now in these two contexts (aka, "savevm", and "colo") sometimes the precopy notifiers will still be invoked, but that's outside the scope of this patch. Signed-off-by: Peter Xu <peterx@redhat.com> Tested-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Juraj Marcin <jmarcin@redhat.com> Link: https://lore.kernel.org/r/20250114230746.3268797-12-peterx@redhat.com Signed-off-by: Fabiano Rosas <farosas@suse.de>
Diffstat (limited to 'rust/qemu-api-macros/src')
0 files changed, 0 insertions, 0 deletions