diff options
| author |   Rick Edgecombe <rick.p.edgecombe@intel.com> | 2026-05-09 15:56:47 +0800 |
|---|---|---|
| committer |   Sean Christopherson <seanjc@google.com> | 2026-05-27 17:19:19 -0700 |
| commit | 41367d77ee4eba4b062835723b1756b0b6a86324 (patch) | |
| tree | 69776547bded0a627caad7229c8b1ee034522b16 /tools/lib/python/kdoc/python_version.py | |
| parent | KVM: x86/tdp_mmu: Centrally propagate to-present/atomic zap updates to external PTEs (diff) | |
KVM: x86/mmu: Drop KVM_BUG_ON() on shared lock to zap child external PTEs
Drop the KVM_BUG_ON() in the KVM MMU core before zapping child external
PTEs, since requiring zapping PTEs to be protected by exclusive mmu_lock is
TDX's specific requirement.
No need to plumb the shared/exclusive info into the remove_external_spte()
op or move the KVM_BUG_ON() to TDX, because
- There's already an assertion of exclusive mmu_lock protection in TDX.
- The KVM_BUG_ON() is a bit redundant given that if there's any bug causing
zapping of leaf PTEs in S-EPT under shared mmu_lock, SEAMCALL failures
due to contention would result in TDX_BUG_ON() in TDX.
Link: https://lore.kernel.org/kvm/aYUarHf3KEwHGuJe@google.com/
Suggested-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Rick Edgecombe <rick.p.edgecombe@intel.com>
Signed-off-by: Yan Zhao <yan.y.zhao@intel.com>
Link: https://patch.msgid.link/20260509075647.4290-1-yan.y.zhao@intel.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions