qemu-e2k/migration
Fiona Ebner 3a8b81f2e6 migration: stop tracking ram writes when cancelling background migration
Currently, it is only done when the iteration finishes successfully.
Not cleaning up the userfaultfd write protection can lead to
symptoms/issues such as the process hanging in memmove or GDB not
being able to attach.

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Message-Id: <20230526115908.196171-1-f.ebner@proxmox.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
2023-06-02 01:03:19 +02:00
..
block-dirty-bitmap.c
block.c
block.h
channel-block.c
channel-block.h
channel.c
channel.h
colo-failover.c
colo.c
dirtyrate.c
dirtyrate.h
exec.c
exec.h
fd.c
fd.h
global_state.c
meson.build
migration-hmp-cmds.c
migration-stats.c
migration-stats.h
migration.c migration: stop tracking ram writes when cancelling background migration 2023-06-02 01:03:19 +02:00
migration.h
multifd-zlib.c
multifd-zstd.c
multifd.c
multifd.h
options.c
options.h
page_cache.c
page_cache.h
postcopy-ram.c
postcopy-ram.h
qemu-file.c
qemu-file.h
ram-compress.c
ram-compress.h
ram.c
ram.h
rdma.c
rdma.h
savevm.c
savevm.h
socket.c
socket.h
target.c
threadinfo.c
threadinfo.h
tls.c
tls.h
trace-events
trace.h
vmstate-types.c
vmstate.c
xbzrle.c
xbzrle.h
yank_functions.c
yank_functions.h