From: Jens Remus <jremus@linux.ibm.com>
To: Matthias Klose <doko@debian.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Binutils <binutils@sourceware.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [RFC] Don't create sframes during build
Date: Thu, 29 Jan 2026 10:13:03 +0100 [thread overview]
Message-ID: <7b45d196-063e-4e76-b08b-ec2bcc111328@linux.ibm.com> (raw)
In-Reply-To: <b3db475e-e84d-4056-9420-bc0acc8b9fe5@debian.org>
On 9/4/2025 4:02 PM, Matthias Klose wrote:
> [ CCing binutils@sourceware.org ]
>
> On 9/4/25 15:18, Sebastian Andrzej Siewior wrote:
>> Hi,
>>
>> gcc in Debian, starting with 15.2.0-2, 14.3.0-6 enables sframe
>> generation. Unless options like -ffreestanding are passed. Since this
>> isn't done, there are a few warnings during compile
>
> If there are other options when sframe shouldn't be enabled, please tell.
>
> Gentoo chose another approach, enabling sframe unconditionally in gas,
> unless disabled by --gsframe=no.
...
>> followed by a boom
>> | LD .tmp_vmlinux1
>> | ld: error: unplaced orphan section `.sframe' from `vmlinux.o'
>>
>> We could drop the sframe during the final link but this does not get rid
>> of the objtool warnings so we would have to ignore them. But we don't
>> need it. So what about the following:
Instead of dropping .sframe for kernel during final link it would be
better not to generate it to save some CPU cycles and disk space.
>>
>> diff --git a/Makefile b/Makefile
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -886,6 +886,8 @@ ifdef CONFIG_CC_IS_GCC
>> KBUILD_CFLAGS += $(call cc-option,--param=allow-store-data-races=0)
>> KBUILD_CFLAGS += $(call cc-option,-fno-allow-store-data-races)
>> endif
>> +# No sframe generation for kernel if enabled by default
>> +KBUILD_CFLAGS += $(call cc-option,-Xassembler --gsframe=no)
>> ifdef CONFIG_READABLE_ASM
>> # Disable optimizations that make assembler listings hard to read.
> This is what I chose for package builds that need disablement of sframe.
What about:
diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -906,6 +906,11 @@ KBUILD_CFLAGS += $(call cc-option,--param=allow-store-data-races=0)
KBUILD_CFLAGS += $(call cc-option,-fno-allow-store-data-races)
endif
+# No .sframe generation for kernel if enabled in assembler by default
+CC_FLAGS_SFRAME := $(call as-option,-Wa$(comma)--gsframe=no)
+KBUILD_CFLAGS += $(CC_FLAGS_SFRAME)
+KBUILD_AFLAGS += $(CC_FLAGS_SFRAME)
+
ifdef CONFIG_READABLE_ASM
# Disable optimizations that make assembler listings hard to read.
# reorder blocks reorders the control in the function
Generation of .sframe in vDSO can override that default. If archs like
arm64 want to enable .sframe for kernel they can introduce a kernel
option (e.g. SFRAME) that changes the default.
Regards,
Jens
--
Jens Remus
Linux on Z Development (D3303)
jremus@de.ibm.com / jremus@linux.ibm.com
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/
next prev parent reply other threads:[~2026-01-29 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 13:18 [RFC] Don't create sframes during build Sebastian Andrzej Siewior
2025-09-04 14:02 ` Matthias Klose
2025-09-04 16:26 ` Matthias Klose
2025-09-04 16:34 ` Sebastian Andrzej Siewior
2025-09-04 17:14 ` Josh Poimboeuf
2026-01-24 12:04 ` Sven Joachim
2026-01-24 19:08 ` Indu
2026-01-27 18:22 ` Indu Bhagat
2026-01-29 9:13 ` Jens Remus [this message]
2026-01-29 22:23 ` Nathan Chancellor
2026-01-30 0:58 ` Indu Bhagat
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=7b45d196-063e-4e76-b08b-ec2bcc111328@linux.ibm.com \
--to=jremus@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=binutils@sourceware.org \
--cc=doko@debian.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jpoimboe@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=peterz@infradead.org \
/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