aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/kvm/paging_tmpl.h
diff options
context:
space:
mode:
authorAnthony Liguori <aliguori@us.ibm.com>2007-10-10 20:25:50 -0400
committerAvi Kivity <avi@qumranet.com>2008-01-30 10:52:51 -0500
commitf67a46f4aa1212b38696ac6b6a82b4323cea61aa (patch)
tree7d9b86dda5a4b4196f0cbd11ef395d7e1c78fbb4 /drivers/kvm/paging_tmpl.h
parent043405e10001fe7aae60c46a57189515f13a6468 (diff)
KVM: MMU: Clean up MMU functions to take struct kvm when appropriate
Some of the MMU functions take a struct kvm_vcpu even though they affect all VCPUs. This patch cleans up some of them to instead take a struct kvm. This makes things a bit more clear. The main thing that was confusing me was whether certain functions need to be called on all VCPUs. Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> Signed-off-by: Avi Kivity <avi@qumranet.com>
Diffstat (limited to 'drivers/kvm/paging_tmpl.h')
-rw-r--r--drivers/kvm/paging_tmpl.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/kvm/paging_tmpl.h b/drivers/kvm/paging_tmpl.h
index 447d2c31f0cb..4f6edf85d13f 100644
--- a/drivers/kvm/paging_tmpl.h
+++ b/drivers/kvm/paging_tmpl.h
@@ -268,11 +268,11 @@ static void FNAME(set_pte_common)(struct kvm_vcpu *vcpu,
268 268
269 spte |= PT_WRITABLE_MASK; 269 spte |= PT_WRITABLE_MASK;
270 if (user_fault) { 270 if (user_fault) {
271 mmu_unshadow(vcpu, gfn); 271 mmu_unshadow(vcpu->kvm, gfn);
272 goto unshadowed; 272 goto unshadowed;
273 } 273 }
274 274
275 shadow = kvm_mmu_lookup_page(vcpu, gfn); 275 shadow = kvm_mmu_lookup_page(vcpu->kvm, gfn);
276 if (shadow) { 276 if (shadow) {
277 pgprintk("%s: found shadow page for %lx, marking ro\n", 277 pgprintk("%s: found shadow page for %lx, marking ro\n",
278 __FUNCTION__, gfn); 278 __FUNCTION__, gfn);