On Wed, Apr 27, 2022 at 11:46:59AM -0700, Kalesh Singh wrote: > On hyp_panic(), the hypervisor dumps the addresses for its stacktrace > entries to a page shared with the host. The host then symbolizes and > prints the hyp stacktrace before panicking itself. > > Example stacktrace: > > [ 122.051187] kvm [380]: Invalid host exception to nVHE hyp! > [ 122.052467] kvm [380]: nVHE HYP call trace: > [ 122.052814] kvm [380]: [<ffff800008f5b550>] > __kvm_nvhe___pkvm_vcpu_init_traps+0x1f0/0x1f0 > [ 122.053865] kvm [380]: [<ffff800008f560f0>] > __kvm_nvhe_hyp_panic+0x130/0x1c0 > [ 122.054367] kvm [380]: [<ffff800008f56190>] > __kvm_nvhe___kvm_vcpu_run+0x10/0x10 > [ 122.054878] kvm [380]: [<ffff800008f57a40>] > __kvm_nvhe_handle___kvm_vcpu_run+0x30/0x50 > [ 122.055412] kvm [380]: [<ffff800008f57d2c>] > __kvm_nvhe_handle_trap+0xbc/0x160 > [ 122.055911] kvm [380]: [<ffff800008f56864>] > __kvm_nvhe___host_exit+0x64/0x64 > [ 122.056417] kvm [380]: ---- end of nVHE HYP call trace ----
This will be really helpful! Reviewed-by: Mark Brown <broo...@kernel.org>
signature.asc
Description: PGP signature
_______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
