diff options
| author | David Matlack <[email protected]> | 2022-01-25 23:05:15 +0000 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2022-02-10 13:50:32 -0500 |
| commit | 115111efd97c6c0e86f8b5904c6624fddcfe4f34 (patch) | |
| tree | e56472f8d5376879f8961fabb462c482e4015747 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 932859a4e0b9fa12ba315e88e3d29f9d2f638916 (diff) | |
KVM: x86/mmu: Check SPTE writable invariants when setting leaf SPTEs
Check SPTE writable invariants when setting SPTEs rather than in
spte_can_locklessly_be_made_writable(). By the time KVM checks
spte_can_locklessly_be_made_writable(), the SPTE has long been since
corrupted.
Note that these invariants only apply to shadow-present leaf SPTEs (i.e.
not to MMIO SPTEs, non-leaf SPTEs, etc.). Add a comment explaining the
restriction and only instrument the code paths that set shadow-present
leaf SPTEs.
To account for access tracking, also check the SPTE writable invariants
when marking an SPTE as an access track SPTE. This also lets us remove
a redundant WARN from mark_spte_for_access_track().
Suggested-by: Sean Christopherson <[email protected]>
Signed-off-by: David Matlack <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions