> From: Wang Han <[email protected]> > > Reliable frame-pointer unwinding needs an explicit way to identify > exception boundaries and the final entry frame. The existing unwinder > infers those boundaries from return addresses, which is too loose for a > future reliable unwinder. > > Add a small metadata frame record to pt_regs and initialize it on > exception entry, kernel stack overflow, kernel thread fork, user fork, > and early idle task setup. The record uses a zero {fp, ra} sentinel plus > a type field so a later unwinder can distinguish a final user-to-kernel > boundary from a nested kernel pt_regs boundary. > > This follows the arm64 metadata frame-record model, adapted to the > RISC-V {fp, ra} frame record convention. > [ ... ] > > Reviewed-by: Shuai Xue <[email protected]> > Assisted-by: Qoder:Qwen-3.8-MAX-Preview > Signed-off-by: Wang Han <[email protected]> > Signed-off-by: Shuai Xue <[email protected]>
Sashiko has reviewed this patch and found no issues. It looks great! -- Sashiko AI review ยท https://sashiko.dev/#/patchset/[email protected]?part=1
