kvm: mmu: Don't expose private memslots to L2
authorJim Mattson <jmattson@google.com>
Wed, 9 May 2018 21:02:05 +0000 (17:02 -0400)
committerPaolo Bonzini <pbonzini@redhat.com>
Mon, 14 May 2018 16:24:26 +0000 (18:24 +0200)
commit3a2936dedd207b99c64bf1507a62a9ae44114220
tree137cbab7344cb910caa650f51cf3fea92ebb85c8
parent1313cc2bd8f6568dd8801feef446afbe43e6d313
kvm: mmu: Don't expose private memslots to L2

These private pages have special purposes in the virtualization of L1,
but not in the virtualization of L2. In particular, L1's APIC access
page should never be entered into L2's page tables, because this
causes a great deal of confusion when the APIC virtualization hardware
is being used to accelerate L2's accesses to its own APIC.

Signed-off-by: Jim Mattson <jmattson@google.com>
Signed-off-by: Krish Sadhukhan <krish.sadhukhan@oracle.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
arch/x86/kvm/mmu.c