mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	"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>, Sam James <sam@gentoo.org>,
	Neal Gompa <neal@gompa.dev>,  Tomas Glozar <tglozar@kernel.org>,
	"Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: [PATCH v2] x86: Start removing X86_X32_ABI
Date: Wed, 08 Jul 2026 12:51:58 +0100	[thread overview]
Message-ID: <8d5e4303fed61478461b8c7b427b644fb46d894b.camel@linuxfoundation.org> (raw)
In-Reply-To: <aeee3456-5d24-4b90-bcb2-5ae85d3a89c7@app.fastmail.com>

On Wed, 2026-07-08 at 13:26 +0200, Arnd Bergmann wrote:
> On Wed, Jul 8, 2026, at 09:36, Sebastian Andrzej Siewior wrote:
> > On 2026-07-08 08:31:30 [+0200], John Paul Adrian Glaubitz wrote:
> > > > 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 by the end of the year, it will removed after the
> > > > last LTS
> > > > kernel this year.
> > > 
> > > As mentioned before, there are still actively maintained Debian
> > > and Gentoo
> > > ports of x32, so I guess the last paragraph is rather subjective.
> > 
> > On the Debian ports side: lacks a browser like firefox or chromium.
> > No
> > native ocaml compiler. libreoffice is not present.
> > Not once released in contrast to kFreeBSD.
> > 
> > This does not look like healthy port that will become eventually a
> > release architecture. To quote the introduction paragraph of
> > ports.d.o:
> > > The goal of this machine is to provide an infrastructure for
> > > unofficial
> > > architectures until they are integrated in the main Debian
> > > archive.
> 
> x32 is a bit different since you can't have a pure x32 distro
> anyway but always need to install an x86_64 distro first
> to get a working kernel and base system before you can choose
> a mix 32-bit and 64-bit packages. This is not that different
> from armhf and i686, which run fine on 64-bit hardware but
> always require you to start with a 64-bit installer. [for
> different reasons though: armhf has an installer but its
> kernel only works on 32-bit machines; i686 kernels can
> theoretically run on older 64-bit hardware but Debian
> no longer provides an installer for it]

FWIW Yocto Project (which cross compiles) can happily build x32 images
and has been able to for years, basically since it was added to the
kernel. It can also mix 32, x32 and 64 bit binaries (and supported n32
on mips too). We do test them nightly under qemu, I think including
boot tests under qemu but I'd have to double check if we still do.

It is very unclear that anyone uses x32 though. If the kernel drops
support, we'll just follow.

Cheers,

Richard


  reply	other threads:[~2026-07-08 11:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 21:22 Sebastian Andrzej Siewior
2026-07-08  5:45 ` Arnd Bergmann
2026-07-08  6:31 ` John Paul Adrian Glaubitz
2026-07-08  7:36   ` Sebastian Andrzej Siewior
2026-07-08 11:26     ` Arnd Bergmann
2026-07-08 11:51       ` Richard Purdie [this message]
2026-07-08 12:22       ` Sam James
2026-07-08 12:44         ` John Paul Adrian Glaubitz
2026-07-08 12:33       ` Sebastian Andrzej Siewior
2026-07-08 13:16         ` Arnd Bergmann
2026-07-08 16:27           ` Maciej W. Rozycki
2026-07-08 20:26             ` David Laight
2026-07-08 23:58               ` Maciej W. Rozycki
2026-07-10 20:59               ` 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=8d5e4303fed61478461b8c7b427b644fb46d894b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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=linux-kernel@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=mingo@redhat.com \
    --cc=neal@gompa.dev \
    --cc=sam@gentoo.org \
    --cc=tglozar@kernel.org \
    --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