]> git.ipfire.org Git - thirdparty/qemu.git/commit
migration: Don't sync volatile memory after migration completes
authorChaney, Ben <bchaney@akamai.com>
Mon, 16 Jun 2025 20:56:50 +0000 (20:56 +0000)
committerMichael Tokarev <mjt@tls.msk.ru>
Sun, 13 Jul 2025 08:36:12 +0000 (11:36 +0300)
commitb4ead907261c0a7228e43feb087c3b543da3620f
tree421a36bb488162fb5efaf157bf8d7d7134cdc951
parenta4e31f5d8ec90a16a250fc39d807f79ce9d99760
migration: Don't sync volatile memory after migration completes

Syncing volatile memory provides no benefit, instead it can cause
performance issues in some cases.  Only sync memory that is marked as
non-volatile after migration completes on destination.

Signed-off-by: Ben Chaney <bchaney@akamai.com>
Fixes: bd108a44bc29 (migration: ram: Switch to ram block writeback)
Link: https://lore.kernel.org/r/1CC43F59-336F-4A12-84AD-DB89E0A17A95@akamai.com
Signed-off-by: Peter Xu <peterx@redhat.com>
(cherry picked from commit 983899eab4939dc4dff67fa4d822c5b4df7eae21)
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
migration/ram.c