summaryrefslogtreecommitdiffstats
path: root/arch/arm
diff options
context:
space:
mode:
authorTakuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>2013-07-04 13:40:29 +0900
committerPaolo Bonzini <pbonzini@redhat.com>2013-07-18 12:29:25 +0200
commite59dbe09f8e6fb8f6ee19dc79d1a2f14299e4cd2 (patch)
tree0de53b1ec2901fd34fdaca56770f0757d9e660e1 /arch/arm
parent85dfe87e24326c472454cc92313ba8c3b4efe53b (diff)
downloadlinux-stable-e59dbe09f8e6fb8f6ee19dc79d1a2f14299e4cd2.tar.gz
linux-stable-e59dbe09f8e6fb8f6ee19dc79d1a2f14299e4cd2.tar.bz2
linux-stable-e59dbe09f8e6fb8f6ee19dc79d1a2f14299e4cd2.zip
KVM: Introduce kvm_arch_memslots_updated()
This is called right after the memslots is updated, i.e. when the result of update_memslots() gets installed in install_new_memslots(). Since the memslots needs to be updated twice when we delete or move a memslot, kvm_arch_commit_memory_region() does not correspond to this exactly. In the following patch, x86 will use this new API to check if the mmio generation has reached its maximum value, in which case mmio sptes need to be flushed out. Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> Acked-by: Alexander Graf <agraf@suse.de> Reviewed-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/arm')
-rw-r--r--arch/arm/kvm/arm.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index 741f66a2edbd..9c697db2787e 100644
--- a/arch/arm/kvm/arm.c
+++ b/arch/arm/kvm/arm.c
@@ -219,6 +219,10 @@ long kvm_arch_dev_ioctl(struct file *filp,
return -EINVAL;
}
+void kvm_arch_memslots_updated(struct kvm *kvm)
+{
+}
+
int kvm_arch_prepare_memory_region(struct kvm *kvm,
struct kvm_memory_slot *memslot,
struct kvm_userspace_memory_region *mem,