On 11/23/2011 05:44 PM, Nadav Har'El wrote: > On Wed, Nov 23, 2011, Nadav Har'El wrote about "Re: [PATCH 02/10] nEPT: MMU context for nested EPT": > > > +static int nested_ept_init_mmu_context(struct kvm_vcpu *vcpu) > > > +{ > > > + int r = kvm_init_shadow_mmu(vcpu, &vcpu->arch.mmu); > > > + > > > + vcpu->arch.nested_mmu.gva_to_gpa = EPT_gva_to_gpa_nested; > > > + > > > + return r; > > > +} > >.. > > I didn't see you actually call this function anywhere - how is it > > supposed to work? > >.. > > It seems we need a fifth case in that function. > >.. > > On second thought, why is this modifying nested_mmu.gva_to_gpa, and not > mmu.gva_to_gpa? Isn't the nested_mmu the L2 CR3, which is *not* in EPT > format, and what we really want to change is the outer mmu, which is > EPT12 and is indeed in EPT format? > Or am I missing something? I think you're right. The key is to look at what ->walk_mmu points at. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html