diff options
author | Sean Christopherson <seanjc@google.com> | 2024-10-10 19:10:37 -0700 |
---|---|---|
committer | Sean Christopherson <seanjc@google.com> | 2024-10-30 14:46:46 -0700 |
commit | 856cf4a60cffbffb31a429761bf605108dbf5ff4 (patch) | |
tree | d10ae3979f593185b3f0cd82acc4f84e603672cc /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | b7ed46b201a41a2f63bc104a66f33c65e1b44fbf (diff) |
KVM: x86/mmu: Don't flush TLBs when clearing Dirty bit in shadow MMU
Don't force a TLB flush when an SPTE update in the shadow MMU happens to
clear the Dirty bit, as KVM unconditionally flushes TLBs when enabling
dirty logging, and when clearing dirty logs, KVM flushes based on its
software structures, not the SPTEs. I.e. the flows that care about
accurate Dirty bit information already ensure there are no stale TLB
entries.
Opportunistically drop is_dirty_spte() as mmu_spte_update() was the sole
caller.
Link: https://lore.kernel.org/r/20241011021051.1557902-6-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions