From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
Mostafa Saleh <smostafa@google.com>
Cc: catalin.marinas@arm.com, will@kernel.org, oliver.upton@linux.dev,
joey.gouly@arm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com,
perret@google.com, keirf@google.com
Subject: Re: [PATCH v2 0/2] Dump instructions on panic for pKVM/nvhe
Date: Mon, 15 Sep 2025 13:07:36 +0100 [thread overview]
Message-ID: <175793804436.660835.10602448198623077028.b4-ty@kernel.org> (raw)
In-Reply-To: <20250909133631.3844423-1-smostafa@google.com>
On Tue, 09 Sep 2025 13:36:29 +0000, Mostafa Saleh wrote:
> This small series, adds support for dumping the faulting instructions on
> panic in pKVM and nvhe, similarly to what the kernel does as follow:
> [ 12.012126] kvm [190]: nVHE hyp BUG at: [<ffff8000811c5f64>] __kvm_nvhe_handle___kvm_vcpu_run+0x4/0x8!
> [ 12.015747] kvm [190]: Cannot dump pKVM nVHE stacktrace: !CONFIG_PROTECTED_NVHE_STACKTRACE
> [ 12.016044] Code: a8c17bfd d50323bf d65f03c0 d503245f (d4210000)
> [ 12.016082] kvm [190]: Hyp Offset: 0xffeff6887fe00000
> [ 12.016325] Kernel panic - not syncing: HYP panic:
> [ 12.016325] PS:204023c9 PC:000f8978013c5f64 ESR:00000000f2000800
> [ 12.016325] FAR:fff00000c016e01c HPFAR:00000000010016e0 PAR:0000000000000000
>
> [...]
Applied to next, thanks!
[1/2] KVM: arm64: Dump instruction on hyp panic
commit: 92b7624fe052ffb0b7b70d96cd514e02e91664a8
[2/2] KVM: arm64: Map hyp text as RO and dump instr on panic
commit: 6f1ece1e868839cf81a28c77e19420ff57df7ecf
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2025-09-15 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 13:36 [PATCH v2 0/2] Dump instructions on panic for pKVM/nvhe Mostafa Saleh
2025-09-09 13:36 ` [PATCH v2 1/2] KVM: arm64: Dump instruction on hyp panic Mostafa Saleh
2025-09-15 10:54 ` Will Deacon
2025-09-09 13:36 ` [PATCH v2 2/2] KVM: arm64: Map hyp text as RO and dump instr on panic Mostafa Saleh
2025-09-15 12:07 ` Marc Zyngier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175793804436.660835.10602448198623077028.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=keirf@google.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=perret@google.com \
--cc=smostafa@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox