aboutsummaryrefslogtreecommitdiffstats
path: root/arch/powerpc/kvm/book3s_hv.c
diff options
context:
space:
mode:
authorTakuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>2013-02-27 05:45:25 -0500
committerMarcelo Tosatti <mtosatti@redhat.com>2013-03-04 18:21:08 -0500
commit8482644aea11e0647867732319ccf35879a9acc2 (patch)
treefbd381ae796ed7af2ff0a7b3d30fdd76ee94d374 /arch/powerpc/kvm/book3s_hv.c
parent7b6195a91d60909a2834ab7181e2b9476e6fe749 (diff)
KVM: set_memory_region: Refactor commit_memory_region()
This patch makes the parameter old a const pointer to the old memory slot and adds a new parameter named change to know the change being requested: the former is for removing extra copying and the latter is for cleaning up the code. Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'arch/powerpc/kvm/book3s_hv.c')
-rw-r--r--arch/powerpc/kvm/book3s_hv.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/powerpc/kvm/book3s_hv.c b/arch/powerpc/kvm/book3s_hv.c
index 80dcc53a1aba..1e521baf9a7d 100644
--- a/arch/powerpc/kvm/book3s_hv.c
+++ b/arch/powerpc/kvm/book3s_hv.c
@@ -1639,12 +1639,12 @@ int kvmppc_core_prepare_memory_region(struct kvm *kvm,
1639 1639
1640void kvmppc_core_commit_memory_region(struct kvm *kvm, 1640void kvmppc_core_commit_memory_region(struct kvm *kvm,
1641 struct kvm_userspace_memory_region *mem, 1641 struct kvm_userspace_memory_region *mem,
1642 struct kvm_memory_slot old) 1642 const struct kvm_memory_slot *old)
1643{ 1643{
1644 unsigned long npages = mem->memory_size >> PAGE_SHIFT; 1644 unsigned long npages = mem->memory_size >> PAGE_SHIFT;
1645 struct kvm_memory_slot *memslot; 1645 struct kvm_memory_slot *memslot;
1646 1646
1647 if (npages && old.npages) { 1647 if (npages && old->npages) {
1648 /* 1648 /*
1649 * If modifying a memslot, reset all the rmap dirty bits. 1649 * If modifying a memslot, reset all the rmap dirty bits.
1650 * If this is a new memslot, we don't need to do anything 1650 * If this is a new memslot, we don't need to do anything