From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@kernel.org>
Subject: Re: [PATCH] x86: Start removing X86_X32_ABI
Date: Wed, 27 May 2026 17:57:30 +0200 [thread overview]
Message-ID: <afa7ec338c931cc6fba15e2d37fcbbfc7670e3d5.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20260523093734.A3AR7reJ@linutronix.de>
Hello Sebastian,
On Sat, 2026-05-23 at 11:37 +0200, Sebastian Andrzej Siewior wrote:
> 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 last syscall for x86_64 is currently at 471. The first x32 starts at
> 512 which leaves 40 new syscalls in between. Without the x32 ABI, those
> syscalls could be used since x32 wouldn't be an option and therefore
> reserved.
>
> Since there is practically no real use for x32, start removing it by
> removing the symbol first, not allowing to enable it. Should nothing
> happening within the next half year, lets remove code bits around August
> after the summer break.
Debian still has an x32 port which is building unstable packages, see [1].
Even Rust works there.
Adrian
> [1] https://buildd.debian.org/status/architecture.php?a=x32&suite=sid
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2026-05-27 15:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 9:37 Sebastian Andrzej Siewior
2026-05-23 21:43 ` H. Peter Anvin
2026-05-26 10:40 ` Sebastian Andrzej Siewior
2026-05-26 15:53 ` H. Peter Anvin
2026-05-26 15:54 ` H. Peter Anvin
2026-05-26 20:43 ` Sebastian Andrzej Siewior
2026-05-31 21:46 ` Arnd Bergmann
2026-06-01 21:44 ` Sebastian Andrzej Siewior
2026-06-01 22:45 ` Arnd Bergmann
2026-05-27 12:02 ` David Laight
2026-06-01 21:29 ` H. Peter Anvin
2026-06-04 20:27 ` Thomas Gleixner
2026-05-27 13:10 ` Sam James
2026-05-27 13:41 ` Neal Gompa
2026-05-27 15:57 ` John Paul Adrian Glaubitz [this message]
2026-06-01 21:12 ` Sebastian Andrzej Siewior
2026-06-01 21:14 ` H. Peter Anvin
2026-05-28 7:05 ` Tomas Glozar
2026-06-01 21:26 ` Sebastian Andrzej Siewior
2026-05-31 22:05 ` Arnd Bergmann
2026-06-02 16:02 ` Maciej W. Rozycki
2026-06-02 16:36 ` Arnd Bergmann
2026-06-05 3:35 ` H. Peter Anvin
2026-07-04 8:08 ` Sebastian Andrzej Siewior
2026-07-04 8:56 ` Arnd Bergmann
2026-06-02 9:48 ` Richard Purdie
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=afa7ec338c931cc6fba15e2d37fcbbfc7670e3d5.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--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®