linux/Documentation/kvm, branch v2.6.35.9Linux kernel source treehttps://git.amat.us/linux/atom/Documentation/kvm?h=v2.6.35.92010-05-19T08:41:09ZKVM: MMU: Segregate shadow pages with different cr0.wp2010-05-19T08:41:09ZAvi Kivityavi@redhat.com2010-05-12T08:48:18Zurn:sha1:3dbe141595faa48a067add3e47bba3205b79d33c
When cr0.wp=0, we may shadow a gpte having u/s=1 and r/w=0 with an spte
having u/s=0 and r/w=1. This allows excessive access if the guest sets
cr0.wp=1 and accesses through this spte.
Fix by making cr0.wp part of the base role; we'll have different sptes for
the two cases and the problem disappears.
Signed-off-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
KVM: Add cpuid.txt file2010-05-19T08:41:07ZGlauber Costaglommer@redhat.com2010-05-11T16:17:47Zurn:sha1:09c9e81366b9167b88ff05cf29fa94dc3553eb3d
This file documents cpuid bits used by KVM.
Signed-off-by: Glauber Costa <glommer@redhat.com>
Acked-by: Zachary Amsden <zamsden@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
KVM: Minor MMU documentation edits2010-05-17T09:19:32ZAvi Kivityavi@redhat.com2010-04-26T08:59:21Zurn:sha1:c4bd09b28907ca17cdb307c32bbcc9882c280feb
Reported by Andrew Jones.
Signed-off-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
KVM: Document KVM_GET_MP_STATE and KVM_SET_MP_STATE2010-05-17T09:19:30ZAvi Kivityavi@redhat.com2010-04-25T12:51:46Zurn:sha1:b843f065481488fd1d1f4ff2179aaf4f300a1358
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
Signed-off-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
KVM: Document mmu2010-05-17T09:19:12ZAvi Kivityavi@redhat.com2010-04-21T13:08:20Zurn:sha1:039091875ce4629d83db64c055528e7b86337d50
Signed-off-by: Avi Kivity <avi@redhat.com>
KVM: Document replacements for KVM_EXIT_HYPERCALL2010-05-17T09:17:22ZAvi Kivityavi@redhat.com2010-04-01T11:39:21Zurn:sha1:647dc49eebad2c30f823cae2bd8204b66c739f9c
Signed-off-by: Avi Kivity <avi@redhat.com>
KVM: PPC: Add OSI hypercall interface2010-05-17T09:17:10ZAlexander Grafagraf@suse.de2010-03-24T20:48:30Zurn:sha1:ad0a048b096ac819f28667602285453468a8d8f9
MOL uses its own hypercall interface to call back into userspace when
the guest wants to do something.
So let's implement that as an exit reason, specify it with a CAP and
only really use it when userspace wants us to.
The only user of it so far is MOL.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Avi Kivity <avi@redhat.com>
KVM: Add support for enabling capabilities per-vcpu2010-05-17T09:17:09ZAlexander Grafagraf@suse.de2010-03-24T20:48:29Zurn:sha1:71fbfd5f38f73515f1516a68fbe04dba198b70f0
Some times we don't want all capabilities to be available to all
our vcpus. One example for that is the OSI interface, implemented
in the next patch.
In order to have a generic mechanism in how to enable capabilities
individually, this patch introduces a new ioctl that can be used
for this purpose. That way features we don't want in all guests or
userspace configurations can just not be enabled and we're good.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Avi Kivity <avi@redhat.com>
KVM: Document KVM_SET_TSS_ADDR2010-05-17T09:16:47ZAvi Kivityavi@redhat.com2010-03-25T10:27:30Zurn:sha1:8a5416db832895b84b85ad0bcbb11d1cce0d3d37
Signed-off-by: Avi Kivity <avi@redhat.com>
KVM: Document KVM_SET_USER_MEMORY_REGION2010-05-17T09:16:46ZAvi Kivityavi@redhat.com2010-03-25T10:16:48Zurn:sha1:0f2d8f4dd0663defff8c1738d33478c1fb65a4f5
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
Signed-off-by: Avi Kivity <avi@redhat.com>