Re: [PATCH v2 7/8] riscv: Kconfig: enable HAVE_RELIABLE_STACKTRACE and HAVE_LIVEPATCH
Shuai Xue <[email protected]> Wed, 3 Jun 2026 09:49:26 +0800
| Newsgroups | org.kernel.vger.live-patching,org.infradead.lists.linux-riscv,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kernel.vger.linux-perf-users,org.kernel.vger.linux-trace-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 5/28/26 4:23 PM, Wang Han wrote: > Now that the metadata frame records, the kunwind state machine and > arch_stack_walk_reliable() are all in place, advertise the capability > to the rest of the kernel: > > * select HAVE_RELIABLE_STACKTRACE under FRAME_POINTER && 64BIT, so > only the configurations that actually have the metadata records > and the FP-based reliable walker enable it. The 64BIT gate is conservative scoping rather than a hard technical requirement: the metadata frame record, kunwind state machine and arch_stack_walk_reliable() all build on RV32 too (and the call_on_irq_stack change in patch 2/8 actually fixes a latent RV32 issue). However, the syscall livepatch selftest and module relocation path have only been exercised on RV64 (QEMU virt SMP=2/4/8). The 64BIT gate can be dropped in a follow-up once RV32 has equivalent coverage. Reviewed-by: Shuai Xue <[email protected]> Thanks. Shuai