diff options
| author | Lorenzo Stoakes (ARM) <ljs@kernel.org> | 2026-09-23 16:15:47 +0100 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2026-09-24 23:28:13 +0100 |
| commit | 2b8033a99631b744a67a6fa5df46d0d7b3b9ab7c (patch) | |
| tree | 542f837b07df503359e0fe59aff19d936f009954 /tools/perf/scripts/python | |
| parent | 18b94675b1fb22b5ce9b607f9de818d916b3da16 (diff) | |
KVM: arm64: Propagate and use esr in s2fd when handling guest aborts
kvm_handle_guest_abort() establishes a kvm_s2_fault_desc data structure,
s2fd, to store and propagate state to either pkvm_mem_abort(), gmem_abort()
or user_mem_abort() handlers.
Each of these, however, examines the Exception Syndrome Register (ESR) via
s2fd->vcpu.
Introduce an s2fd->esr field to abstract this and propagate it to callers.
The value of this (beyond refactoring) is to be able to later generate
faults with a synthetic esr, specifically to implement stage 2 page table
pre-faulting.
Abort handlers which use kvm_s2_fault_desc - gmem_abort() and
user_mem_abort() - now only reference s2fd->esr and do not look it up in
any other way, which makes it safe to pass a synthetic s2fd->esr value to
these functions.
No functional change intended.
Reviewed-by: Oliver Upton <oupton@kernel.org>
Signed-off-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
Reviewed-by: Fuad Tabba <fuad.tabba@linux.dev>
Tested-by: Fuad Tabba <fuad.tabba@linux.dev>
Link: https://patch.msgid.link/20260923-kvm-arm-prefault-v4-4-d4b0b4dfa8c3@kernel.org
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
