| commit | 1bfbac4ee16e2ea95d087e0926727d9a113b483e | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Mon, 23 Mar 2015 09:57:21 +0000 (23 10:57 +0100) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Fri, 5 Jun 2015 15:09:59 +0000 (5 17:09 +0200) | ||
| tree | 5fa5cf563091faa7f98552e2e65c68b5b6600e4e | treesnapshot (tar.gz zip) |
| parent | 6f6a5ef3e429f92f987678ea8c396aab4dc6aa19 | commitdiff |
kvm: remove special handling of DIRTY_MEMORY_MIGRATION in the dirty log mask
One recent example is commit 4cc856f (kvm-all: Sync dirty-bitmap from
kvm before kvm destroy the corresponding dirty_bitmap, 2015-04-02).
Another performance problem is that KVM keeps tracking dirty pages
after a failed live migration, which causes bad performance due to
disallowing huge page mapping.
Thanks to the previous patch, KVM can now stop hooking into
log_global_start/stop. This simplifies the KVM code noticeably.
Reported-by: Wanpeng Li <wanpeng.li@linux.intel.com>
Reported-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
One recent example is commit 4cc856f (kvm-all: Sync dirty-bitmap from
kvm before kvm destroy the corresponding dirty_bitmap, 2015-04-02).
Another performance problem is that KVM keeps tracking dirty pages
after a failed live migration, which causes bad performance due to
disallowing huge page mapping.
Thanks to the previous patch, KVM can now stop hooking into
log_global_start/stop. This simplifies the KVM code noticeably.
Reported-by: Wanpeng Li <wanpeng.li@linux.intel.com>
Reported-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| kvm-all.c | diffblobblamehistory |