diff options
| author | Sean Christopherson <[email protected]> | 2021-06-09 16:42:23 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2021-06-17 13:09:51 -0400 |
| commit | 272b0a998d084e7667284bdd2d0c675c6a2d11de (patch) | |
| tree | 7c791d80185f4e4c01b3ba778b3b7b3b7f75af55 /tools/perf/scripts/python | |
| parent | 0e75225dfa4c5d5d51291f54a3d2d5895bad38da (diff) | |
KVM: nVMX: Don't clobber nested MMU's A/D status on EPTP switch
Drop bogus logic that incorrectly clobbers the accessed/dirty enabling
status of the nested MMU on an EPTP switch. When nested EPT is enabled,
walk_mmu points at L2's _legacy_ page tables, not L1's EPT for L2.
This is likely a benign bug, as mmu->ept_ad is never consumed (since the
MMU is not a nested EPT MMU), and stuffing mmu_role.base.ad_disabled will
never propagate into future shadow pages since the nested MMU isn't used
to map anything, just to walk L2's page tables.
Note, KVM also does a full MMU reload, i.e. the guest_mmu will be
recreated using the new EPTP, and thus any change in A/D enabling will be
properly recognized in the relevant MMU.
Fixes: 41ab93727467 ("KVM: nVMX: Emulate EPTP switching for the L1 hypervisor")
Signed-off-by: Sean Christopherson <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions