summaryrefslogtreecommitdiff
path: root/include/exec
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2016-09-22 16:08:31 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2016-09-27 11:57:29 +0200
commit9c1f8f4493e8355d0e48f7d1eebdf86893ba082d (patch)
treee47020351bb35ddcba713a692c853a9fad882fce /include/exec
parentcc9d8a3b2c41c22fb09f90f3085e6036c199c3ca (diff)
downloadqemu-9c1f8f4493e8355d0e48f7d1eebdf86893ba082d.tar.gz
qemu-9c1f8f4493e8355d0e48f7d1eebdf86893ba082d.tar.bz2
qemu-9c1f8f4493e8355d0e48f7d1eebdf86893ba082d.zip
migration: sync all address spaces
Migrating a VM during reboot sometimes results in differences between the source and destination in the SMRAM area. This is because migration_bitmap_sync() only fetches from KVM the dirty log of address_space_memory. SMRAM memory slots are ignored and the modifications to SMRAM are not sent to the destination. Reported-by: He Rongguang <herongguang.he@huawei.com> Reviewed-by: He Rongguang <herongguang.he@huawei.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'include/exec')
-rw-r--r--include/exec/memory.h7
1 files changed, 3 insertions, 4 deletions
diff --git a/include/exec/memory.h b/include/exec/memory.h
index a3f988b640..10d7eacc40 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -1188,12 +1188,11 @@ MemoryRegionSection memory_region_find(MemoryRegion *mr,
hwaddr addr, uint64_t size);
/**
- * address_space_sync_dirty_bitmap: synchronize the dirty log for all memory
+ * memory_global_dirty_log_sync: synchronize the dirty log for all memory
*
- * Synchronizes the dirty page log for an entire address space.
- * @as: the address space that contains the memory being synchronized
+ * Synchronizes the dirty page log for all address spaces.
*/
-void address_space_sync_dirty_bitmap(AddressSpace *as);
+void memory_global_dirty_log_sync(void);
/**
* memory_region_transaction_begin: Start a transaction.