diff options
| author | Sean Christopherson <[email protected]> | 2021-02-25 12:47:32 -0800 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2021-03-15 04:43:38 -0400 |
| commit | a54aa15c6bda3ca7e2f9e040ba968a1da303e24f (patch) | |
| tree | 7201bc0359d118bc7a851b2a9ad27f8dec71e353 /tools/perf/scripts/python | |
| parent | 30ab5901da57f16b919edfc4c5f8edf9311ba9c3 (diff) | |
KVM: x86/mmu: Handle MMIO SPTEs directly in mmu_set_spte()
Now that it should be impossible to convert a valid SPTE to an MMIO SPTE,
handle MMIO SPTEs early in mmu_set_spte() without going through
set_spte() and all the logic for removing an existing, valid SPTE.
The other caller of set_spte(), FNAME(sync_page)(), explicitly handles
MMIO SPTEs prior to calling set_spte().
This simplifies mmu_set_spte() and set_spte(), and also "fixes" an oddity
where MMIO SPTEs are traced by both trace_kvm_mmu_set_spte() and
trace_mark_mmio_spte().
Note, mmu_spte_set() will WARN if this new approach causes KVM to create
an MMIO SPTE overtop a valid SPTE.
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