diff options
| author | Fabiano Rosas <farosas@suse.de> | 2024-08-27 14:45:58 -0300 |
|---|---|---|
| committer | Fabiano Rosas <farosas@suse.de> | 2024-09-03 16:24:35 -0300 |
| commit | d7e58f412cf6c5426efda60558f0ccfbf709f646 (patch) | |
| tree | b149ccc8fa2ae8c69d88ffafcbdc7c3f8579ef4e /hw/m68k/next-cube.c | |
| parent | 87bb9e953e6729920701dbc439a498586ae7e305 (diff) | |
| download | qemu-d7e58f412cf6c5426efda60558f0ccfbf709f646.zip qemu-d7e58f412cf6c5426efda60558f0ccfbf709f646.tar.gz qemu-d7e58f412cf6c5426efda60558f0ccfbf709f646.tar.bz2 | |
migration/multifd: Don't send ram data during SYNC
Skip saving and loading any ram data in the packet in the case of a
SYNC. This fixes a shortcoming of the current code which requires a
reset of the MultiFDPages_t fields right after the previous
pending_job finishes, otherwise the very next job might be a SYNC and
multifd_send_fill_packet() will put the stale values in the packet.
By not calling multifd_ram_fill_packet(), we can stop resetting
MultiFDPages_t in the multifd core and leave that to the client code.
Actually moving the reset function is not yet done because
pages->num==0 is used by the client code to determine whether the
MultiFDPages_t needs to be flushed. The subsequent patches will
replace that with a generic flag that is not dependent on
MultiFDPages_t.
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Fabiano Rosas <farosas@suse.de>
Diffstat (limited to 'hw/m68k/next-cube.c')
0 files changed, 0 insertions, 0 deletions