diff options
| author | Oliver Upton <oupton@kernel.org> | 2026-06-02 16:54:47 -0700 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2026-06-03 21:06:43 +0100 |
| commit | 5949004d7032767e8fde1e8c986a33f241b2a192 (patch) | |
| tree | 3bb299fa20f05f490a31c06e68f22645cc409877 /tools/lib/python | |
| parent | 9f76b039a72d7e06374aa96862f0232ed53f7787 (diff) | |
KVM: arm64: nv: Fully update VNCR fixmap state in kvm_translate_vncr()
kvm_translate_vncr() first invalidates the pseudo-TLB entry and
corresponding fixmap in anticipation of installing a new translation.
While the fixmap invalidation does clear the mapping from host stage-1,
it does not clear the L1_VNCR_MAPPED flag. Depending on the state of the
VNCR TLB at vcpu_put(), this could potentially precipitate a BUG_ON() if
vt->cpu is reset.
Share a helper with kvm_vcpu_put_hw_mmu(), ensuring that KVM's view of
the VNCR fixmap is in sync with the state of the VNCR TLB. Give it a
slightly verbose name to make it obvious that it is meant to be used
local to a CPU, unlike other VNCR TLB maintenance.
Fixes: 069a05e535496 ("KVM: arm64: nv: Handle VNCR_EL2-triggered faults")
Signed-off-by: Oliver Upton <oupton@kernel.org>
Link: https://patch.msgid.link/20260602235450.103057-3-oupton@kernel.org
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
