Shadow MMU state preserved across kvm_mmu_zap_all?

Hello, I'm trying to track down a bug I'm observing in a branched version of kvm I'm using for research. I'm hoping someone might be able to point me int to the right direction as I haven't had any luck with it on my own. Here are the details: I have made some changes to kvm that enable

Re: KVM Page Fault Question

levels allowed to be shadowed multiple times? Thank you! Marek Marek Avi Kivity wrote: On 04/22/2010 08:26 AM, Marek Olszewski wrote: Under VMX without EPT, I do not seeing any VM Exits due to task switches. Is there a way to enable these? I'm looking to intercept the guest whenever

Re: KVM Page Fault Question

Under VMX without EPT, I do not seeing any VM Exits due to task switches. Is there a way to enable these? I'm looking to intercept the guest whenever it does a iret. Thanks! Marek Avi Kivity wrote: (re-adding list) On 04/02/2010 07:01 PM, Marek Olszewski wrote: Thanks for the fast

KVM Page Fault Question

When using VMX without EPT, is it ever possible for a guest to receive a page fault without it first appearing (and being reinjected) in KVM? I'm seeing some strange behavior where accesses to mprotected (but yet to be accessed) memory causes a fault in the guest OS, that I cannot see KVM

Re: Shadow page table questions

It doesn't, and there are often multiple shadow pages per guest page, distinguished by their sp-role field. Oh, great! Does this mean that there is already a mechanism for synchronizing all shadow pages shadowing the same guest when such a guest page changes? Marek -- To unsubscribe from

Re: Shadow page table questions

when a guest thread makes a change, but I'm wondering if there is anything else. Does the reverse mapping data structure you have assume that there is only one shadow page per guest page? Thanks! Marek Avi Kivity wrote: On 03/10/2010 06:57 AM, Marek Olszewski wrote: Hello, I was wondering

Shadow page table questions

Hello, I was wondering if someone could point me to some documentation that explains the basic non-nested-paging shadow page table algorithm/strategy used by KVM. I understand that KVM caches shadow page tables across context switches and that there is a reverse mapping and page protection

Avoiding the page cache?

Hello, I'm trying to start using kvm to do some research here at MIT. I would like to try out some interesting page mapping ideas we have that would be easier to try out in a hypervisor than inside the linux kernel. However, I would like to start hacking a simple version of kvm that