Xiao Guangrong 4d8b81abc4 KVM: introduce readonly memslot ... In current code, if we map a readonly memory space from host to guest and the page is not currently mapped in the host, we will get a fault pfn and async is not allowed, then the vm will crash We introduce readonly memory region to map ROM/ROMD to the guest, read access is happy for readonly memslot, write access on readonly memslot will cause KVM_EXIT_MMIO exit Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com> Signed-off-by: Avi Kivity <avi@redhat.com>		2012-08-22 15:09:03 +03:00
..
api.txt	KVM: introduce readonly memslot	2012-08-22 15:09:03 +03:00
cpuid.txt	KVM: fix cpuid eax for KVM leaf	2012-05-06 15:51:56 +03:00
hypercalls.txt	KVM: Add documentation on hypercalls	2012-08-13 17:39:59 -03:00
locking.txt	KVM: MMU: document mmu-lock and fast page fault	2012-07-11 16:51:23 +03:00
mmu.txt	Documentation: Fix multiple typo in Documentation	2012-03-07 16:08:24 +01:00
msr.txt	KVM: eoi msi documentation	2012-06-25 12:40:34 +03:00
nested-vmx.txt	KVM: nVMX: Documentation	2011-07-12 13:15:22 +03:00
ppc-pv.txt	KVM: Add ppc hypercall documentation	2012-08-13 17:39:59 -03:00
review-checklist.txt
timekeeping.txt