On 2/11/2026 3:13 PM, Jens Remus wrote: > > This enables generation of SFrame V3 stack trace information for VDSO on > x86-64. It's a continuation of Josh's and Steve's work: > > https://lore.kernel.org/all/[email protected]/ > https://lore.kernel.org/all/[email protected]/ > > This series focuses only on the VDSO code. They are helpful fixes > and updates that doesn't rely on sframes (although the last patch > is sframe related). > > This series applies on top of tip:x86/entry: > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/entry > > Like the unwind user sframe series [1] it depends on the binutils 2.46 > release to be used to build the VDSO with SFrame V3 stack trace > information (using the assembler option --gsframe-3). > > [1]: [PATCH v13 00/18] unwind_deferred: Implement sframe handling, > https://lore.kernel.org/all/[email protected]/ > > Changes in v9 (see indivicual patch notes): > - Always define KEEP_SFRAME to either true/false in specific VDSO linker > scripts and use #if instead of #ifdef in common one. (Peter) > - Reword patch 6 commit message to provide more details. > - Note: Binutils 2.46 with SFrame V3 support has been released. Hello H. Peter,
how do we proceed with this series? I got your Acked-by for all but the last patch, which has all of your review feedback integrated in v9. Is there a different tree I should rebase it on? Thanks and regards, Jens -- Jens Remus Linux on Z Development (D3303) [email protected] / [email protected] IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der Gesellschaft: Ehningen; Registergericht: Amtsgericht Stuttgart, HRB 243294 IBM Data Privacy Statement: https://www.ibm.com/privacy/
