On Wed, 02 Apr 2008 10:22:45 -0500 Anthony Liguori <[EMAIL PROTECTED]> wrote:
> We can then obtain the faulting > virtual address from CR2 in the host and walk the guest's page table to > determine what guest physical address should be mapped at that guest > virtual address (if any at all). > [...] > I think what you're missing is that while the guest is running, it's CR3 > does not point to it's own page table but rather to the shadow page > table. We intercept CR3 reads to pretend to the guest that it's page > table is, in fact, installed but it's really the shadow page table > that's in the hardware register. Thank you very much for the explanations. You're right, I missed that CR3 points to the shadow page table. So it means that guest page table is not really used for translating guest virtual address to real physical address. If the guest page table is not used, why hyupervisor must find the guest physical address? I mean if with the shadow page table we can translate guest virtual address to real physical address it's not necessary to know the guest physical address. Is it only for checks? Regards, Guillaume ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
