diff options
author | 2022-02-26 00:15:25 +0000 | |
---|---|---|
committer | 2022-03-08 09:31:51 -0500 | |
commit | c8e5a0d0e9bcc67b095e44c8f4420d4ed08ff06a (patch) | |
tree | d13c6b4f6726ddf74afd4cd070422838d04b5beb /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | KVM: x86/mmu: do not allow readers to acquire references to invalid roots (diff) | |
download | linux-dev-c8e5a0d0e9bcc67b095e44c8f4420d4ed08ff06a.tar.xz linux-dev-c8e5a0d0e9bcc67b095e44c8f4420d4ed08ff06a.zip |
KVM: x86/mmu: Check for !leaf=>leaf, not PFN change, in TDP MMU SP removal
Look for a !leaf=>leaf conversion instead of a PFN change when checking
if a SPTE change removed a TDP MMU shadow page. Convert the PFN check
into a WARN, as KVM should never change the PFN of a shadow page (except
when its being zapped or replaced).
From a purely theoretical perspective, it's not illegal to replace a SP
with a hugepage pointing at the same PFN. In practice, it's impossible
as that would require mapping guest memory overtop a kernel-allocated SP.
Either way, the check is odd.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Ben Gardon <bgardon@google.com>
Message-Id: <20220226001546.360188-8-seanjc@google.com>
Reviewed-by: Mingwei Zhang <mizhang@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions