From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Tancred <alex@narraduct.com>
Cc: "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
"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: Sun, 11 Oct 2026 19:19:46 +0200 [thread overview]
Message-ID: <20261011171946.gMv8V9Ck@breakpoint.cc> (raw)
In-Reply-To: <7f315c7a-0fd1-4f7e-93bb-703d4107aa5a@narraduct.com>
On 2026-10-09 20:13:55 [-0600], Tancred wrote:
>
>
> On 10/8/26 03:07, Sebastian Andrzej Siewior wrote:
> > 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).
> >
> > Since there is practically no real use for x32
>
> I only recently discovered x32 and built a Desktop (with all daemons and
> utilities running 10-30% smaller and some a bit faster, with 64 bit
> libraries for eg. Firefox.) My experiment should definitely not decide
> anything, but how much real-world use would be sufficient to justify
> continued presence (more complex compat code)?
"a bit faster" needs actual numbers to justify. One examples was quicker
gcc but I don't see a x32 compile farm leveraging this benefit.
Smaller binaries sounds like a benefit from storage point of view but
then if you need also 64bit binaries (and libs) for things like firefox
then the advantage is probably more than gone.
Also, Adrian keeps pointing out that Debian has a Debian port of x32.
Without an official release (and installer) there will not be security
updates of packages. Without security updates for a "stable release" one
is stuck with Sid which has "latest" of all packages. That is usually
not something for non-developers.
> - Alex Alejandre
Sebastian
next prev parent reply other threads:[~2026-10-11 17: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
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 [this message]
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=20261011171946.gMv8V9Ck@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=alex@narraduct.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=hpa@zytor.com \
--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=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®