aboutsummaryrefslogtreecommitdiff
path: root/migration/ram.h
diff options
context:
space:
mode:
authorLukas Straub <lukasstraub2@web.de>2020-05-11 13:10:51 +0200
committerDr. David Alan Gilbert <dgilbert@redhat.com>2020-06-01 18:44:27 +0100
commit24fa16f8cc374935458672b027829180ea4b4460 (patch)
tree68f47253ba485939fc2a7e8e07cca501c4c5bc99 /migration/ram.h
parent786d8b8e38b134f99556e08047e016563b7063f9 (diff)
downloadqemu-24fa16f8cc374935458672b027829180ea4b4460.zip
qemu-24fa16f8cc374935458672b027829180ea4b4460.tar.gz
qemu-24fa16f8cc374935458672b027829180ea4b4460.tar.bz2
migration/colo.c: Flush ram cache only after receiving device state
If we suceed in receiving ram state, but fail receiving the device state, there will be a mismatch between the two. Fix this by flushing the ram cache only after the vmstate has been received. Signed-off-by: Lukas Straub <lukasstraub2@web.de> Message-Id: <3289d007d494cb0e2f05b1cf4ae6a78d300fede3.1589193382.git.lukasstraub2@web.de> Reviewed-by: zhanghailiang <zhang.zhanghailiang@huawei.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'migration/ram.h')
-rw-r--r--migration/ram.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/migration/ram.h b/migration/ram.h
index 5ceaff7..2eeaacf 100644
--- a/migration/ram.h
+++ b/migration/ram.h
@@ -65,6 +65,7 @@ int ram_dirty_bitmap_reload(MigrationState *s, RAMBlock *rb);
/* ram cache */
int colo_init_ram_cache(void);
+void colo_flush_ram_cache(void);
void colo_release_ram_cache(void);
void colo_incoming_start_dirty_log(void);