Juan Quintela 73208a336e migration: Make dirty_bytes_last_sync atomic ... As we set its value, it needs to be operated with atomics. We rename it from remaining to better reflect its meaning. Statistics always return the real reamaining bytes. This was used to store how much pages where dirty on the previous generation, so we can calculate the expected downtime as: dirty_bytes_last_sync / current_bandwith. If we use the actual remaining bytes, we would see a very small value at the end of the iteration. Signed-off-by: Juan Quintela <quintela@redhat.com> Reviewed-by: Peter Xu <peterx@redhat.com> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> --- I am open to use ram_bytes_remaining() in its only use and be more "optimistic" about the downtime. Don't use __nocheck() functions. Use stat64_get() now that it exists.		2023-04-27 16:39:54 +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.c	migration: Make dirty_bytes_last_sync atomic	2023-04-27 16:39:54 +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.c	migration: Make dirty_bytes_last_sync atomic	2023-04-27 16:39:54 +02:00
ram.h	migration: Make dirty_bytes_last_sync atomic	2023-04-27 16:39:54 +02:00
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