From: "H. Peter Anvin" <hpa@zytor.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: "Sebastian Andrzej Siewior" <sebastian@breakpoint.cc>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
"Bill Wendling" <morbo@google.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Ingo Molnar" <mingo@redhat.com>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Justin Stitt" <justinstitt@google.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Neal Gompa" <neal@gompa.dev>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Richard Purdie" <richard.purdie@linuxfoundation.org>,
"Sam James" <sam@gentoo.org>, "Shuah Khan" <shuah@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Tomas Glozar" <tglozar@kernel.org>, "Willy Tarreau" <w@1wt.eu>,
x86@kernel.org, "Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH v4 2/2] x86: Start removing X86_X32_ABI
Date: Thu, 08 Oct 2026 14:15:39 +0200 [thread overview]
Message-ID: <2B66CB7E-2302-470F-A3B5-0566DCF2A826@zytor.com> (raw)
In-Reply-To: <20261008-x32_removal-v4-2-d389a193c506@breakpoint.cc>
On October 8, 2026 11:07:43 AM GMT+02:00, Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
>
>From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>
>The x32 ABI was introduced in v3.4 to leverage the additional registers
>which were available on x86_64 but not on i386 while keeping the smaller
>32bit pointers.
>
>This did not take off. The memory usage usually knows no limit and the
>better performance did not reach a point where certain workloads widely
>move to x32 and use it exclusively. In the meantime Debian introduced a
>patch to disable x32 by default (so it has to be enabled at boot time on
>the command line) because they are afraid of the increased attack
>surface. Fedora as far as I tell has X32 disabled (looking at 7.0-rc5
>rpm in rawhide).
>
>The syscall range >512 used by x32 can not be reused because on earlier
>kernels (before v5.4 with x32 enabled, see commit 6365b842aae4
>("x86/syscalls: Split the x32 syscalls into their own table") it is not
>obvious if the syscall is for x86-64 and not implemented or meant for
>x32.
>What can be removed are the special compat cases due to different
>alignment.
>
>Since there is practically no real use for x32, start removing it by
>marking the symbol as BROKEN so it is not possible to enable by default.
>It will remain around in the last LTS kernel of this year and then it
>will be removed.
>
>Acked-by: Arnd Bergmann <arnd@arndb.de>
>Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>---
> arch/x86/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>index 15fd9ec5ecacb..21a6863e14e7a 100644
>--- a/arch/x86/Kconfig
>+++ b/arch/x86/Kconfig
>@@ -3104,7 +3104,7 @@ config IA32_EMULATION_DEFAULT_DISABLED
>
> config X86_X32_ABI
> bool "x32 ABI for 64-bit mode"
>- depends on X86_64
>+ depends on X86_64 && BROKEN
> # llvm-objcopy does not convert x86_64 .note.gnu.property or
> # compressed debug sections to x86_x32 properly:
> # https://github.com/ClangBuiltLinux/linux/issues/514
>
Acked-by: H. Peter Anvin (Rosaic) <hpa@zytor.com>
next prev parent reply other threads:[~2026-10-08 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 9:07 [PATCH v4 0/2] " Sebastian Andrzej Siewior
2026-10-08 9:07 ` [PATCH v4 1/2] selftests/nolibc: remove the x32 testcase Sebastian Andrzej Siewior
2026-10-08 12:15 ` H. Peter Anvin
2026-10-08 9:07 ` [PATCH v4 2/2] x86: Start removing X86_X32_ABI Sebastian Andrzej Siewior
2026-10-08 12:15 ` H. Peter Anvin [this message]
2026-10-10 2:13 ` Tancred
2026-10-10 6:51 ` H. Peter Anvin
2026-10-10 7:28 ` John Paul Adrian Glaubitz
2026-10-10 10:55 ` H. Peter Anvin
2026-10-11 17:19 ` Sebastian Andrzej Siewior
2026-10-11 17:38 ` Willy Tarreau
2026-10-11 20:07 ` H. Peter Anvin
2026-10-10 6:38 ` H. Peter Anvin
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=2B66CB7E-2302-470F-A3B5-0566DCF2A826@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=macro@orcam.me.uk \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=neal@gompa.dev \
--cc=richard.purdie@linuxfoundation.org \
--cc=sam@gentoo.org \
--cc=sebastian@breakpoint.cc \
--cc=shuah@kernel.org \
--cc=tglozar@kernel.org \
--cc=tglx@kernel.org \
--cc=w@1wt.eu \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®