ram_addr: tweaks to xen_modified_memory
commit49dfcec40349245ad365964468b67e132c3cedc7
authorPaolo Bonzini <pbonzini@redhat.com>
Mon, 23 Mar 2015 10:35:19 +0000 (23 11:35 +0100)
committerPaolo Bonzini <pbonzini@redhat.com>
Fri, 5 Jun 2015 15:09:59 +0000 (5 17:09 +0200)
tree91a2e4f16e684fa413880ebc80b1e2c4619ae0a1
parent1bfbac4ee16e2ea95d087e0926727d9a113b483e
ram_addr: tweaks to xen_modified_memory

Invoke xen_modified_memory from cpu_physical_memory_set_dirty_range_nocode;
it is akin to DIRTY_MEMORY_MIGRATION, so set it together with that bitmap.
The remaining call from invalidate_and_set_dirty's "else" branch will go
away soon.

Second, fix the second argument to the function in the
cpu_physical_memory_set_dirty_lebitmap call site.  That function is only used
by KVM, but it is better to be clean anyway.

Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
exec.c
include/exec/ram_addr.h