On 17.07.2025 13:09, Jens Remus wrote: > On 17.07.2025 01:01, Josh Poimboeuf wrote: >> On Thu, Jul 10, 2025 at 06:35:13PM +0200, Jens Remus wrote: >>> +++ b/arch/Kconfig >>> @@ -450,6 +450,11 @@ config HAVE_UNWIND_USER_SFRAME >>> bool >>> select UNWIND_USER >>> >>> +config HAVE_USER_RA_REG >>> + bool >>> + help >>> + The arch passes the return address (RA) in user space in a register. >> >> How about "HAVE_UNWIND_USER_RA_REG" so it matches the existing >> namespace? > > Ok. I am open to any improvements.
Thinking about this again I realized that the config option actually serves two purposes: 1. Enable code (e.g. unwind user) to determine the presence of the new user_return_address(). That is where I derived the name from. 2. Enable unwind user (sframe) to behave differently, if an architecture has/uses a RA register (unlike x86, which solely uses the stack). I think the primary notion is that an architecture has/uses a register for the return address and thus provides user_return_address(). What consumers such as unwind user do with that info is secondary. Thoughts? Thanks and regards, Jens -- Jens Remus Linux on Z Development (D3303) +49-7031-16-1128 Office jre...@de.ibm.com IBM IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294 IBM Data Privacy Statement: https://www.ibm.com/privacy/
