diff options
author | Paolo Bonzini <[email protected]> | 2017-08-17 18:36:58 +0200 |
---|---|---|
committer | Radim Krčmář <[email protected]> | 2017-08-18 14:37:49 +0200 |
commit | 9034e6e89526627094ff80df05db54f76a6f8fa8 (patch) | |
tree | e23bf95f2a0463e93a7fd04268819759cf53ff09 /tools/perf/scripts/python/stackcollapse.py | |
parent | 618232e2196a6db1ed66b5e1ec049e5c46480f49 (diff) |
KVM: x86: fix use of L1 MMIO areas in nested guests
There is currently some confusion between nested and L1 GPAs. The
assignment to "direct" in kvm_mmu_page_fault tries to fix that, but
it is not enough. What this patch does is fence off the MMIO cache
completely when using shadow nested page tables, since we have neither
a GVA nor an L1 GPA to put in the cache. This also allows some
simplifications in kvm_mmu_page_fault and FNAME(page_fault).
The EPT misconfig likewise does not have an L1 GPA to pass to
kvm_io_bus_write, so that must be skipped for guest mode.
Signed-off-by: Paolo Bonzini <[email protected]>
Reviewed-by: David Hildenbrand <[email protected]>
[Changed comment to say "GPAs" instead of "L1's physical addresses", as
per David's review. - Radim]
Signed-off-by: Radim Krčmář <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions