KVM: arm64: Prepare non-protected nVHE hypervisor stacktrace
authorKalesh Singh <kaleshsingh@google.com>
Tue, 26 Jul 2022 07:37:42 +0000 (00:37 -0700)
committerMarc Zyngier <maz@kernel.org>
Tue, 26 Jul 2022 09:49:27 +0000 (10:49 +0100)
commit879e5ac7b2e4db05799a905b5a07fc9e5dedf651
treedc0aba616cba53b426932a253affba8589311625
parent573e1e8275f7167ddd533c6e4e0f500f8be4d974
KVM: arm64: Prepare non-protected nVHE hypervisor stacktrace

In non-protected nVHE mode (non-pKVM) the host can directly access
hypervisor memory; and unwinding of the hypervisor stacktrace is
done from EL1 to save on memory for shared buffers.

To unwind the hypervisor stack from EL1 the host needs to know the
starting point for the unwind and information that will allow it to
translate hypervisor stack addresses to the corresponding kernel
addresses. This patch sets up this book keeping. It is made use of
later in the series.

Signed-off-by: Kalesh Singh <kaleshsingh@google.com>
Reviewed-by: Fuad Tabba <tabba@google.com>
Tested-by: Fuad Tabba <tabba@google.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220726073750.3219117-10-kaleshsingh@google.com
arch/arm64/include/asm/kvm_asm.h
arch/arm64/kvm/hyp/nvhe/stacktrace.c
arch/arm64/kvm/hyp/nvhe/switch.c