]> git.ipfire.org Git - thirdparty/qemu.git/commit
projects / thirdparty / qemu.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 430671f) | patch
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)
committerPeter Xu <peterx@redhat.com>
Mon, 23 Jun 2025 20:03:59 +0000 (16:03 -0400)
commit983899eab4939dc4dff67fa4d822c5b4df7eae21
treea1cb7daa71e27bfe114fd9f22729e3e709624631tree | snapshot
parent430671f52669e84c176c4d3b9091b88b51f542fbcommit | diff
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>
migration/ram.c diff | blob | blame | history
Mirror of https://git.qemu.org/git/qemu.git