From: David Laight <david.laight.linux@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
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>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH v2] x86: Start removing X86_X32_ABI
Date: Wed, 8 Jul 2026 21:26:28 +0100 [thread overview]
Message-ID: <20260708212628.4083e180@pumpkin> (raw)
In-Reply-To: <alpine.DEB.2.21.2607081716140.18760@angie.orcam.me.uk>
On Wed, 8 Jul 2026 17:27:46 +0100 (BST)
"Maciej W. Rozycki" <macro@orcam.me.uk> wrote:
> On Wed, 8 Jul 2026, Arnd Bergmann wrote:
>
> > As I understand, it's a policy in Debian for debian-installer and
> > the kernel packages to only provide kernels for the native
> > architecture, i.e. 64-bit x86 kernels are only packaged for
> > amd64 and not x32 or i686, and 64-bit Arm kernels are only
> > packaged for arm64 but not armhf or formerly armel.
>
> Weird, x32 vs x64 for the Intel ISA or say n32 vs n64 for the MIPS ISA
> are psABI variants rather than architectures. All are native, just using
> different register usage conventions.
IIRC n32 just uses the 32bit system calls.
x32 can't do that due to the differing alignment of u64.
So the x86-64 kernel has to have three sets of system call wrappers (etc).
David
>
> And the kernel is a bare metal application, it has nothing to do with the
> userland as far as the user psABI is concerned. It could use yet another
> psABI and I suspect this is the case at least for some of the Linux ports
> (`-mregparm=' GCC option comes immediately to mind). Insisting that the
> same compilation options are used for the kernel as with all the userland
> packages in a distribution seems artificial and unreasonable to me.
>
> BTW, at least with n32 the MIPS architecture permits CPU implementations
> that only support that psABI and not n64. Never implemented, I believe,
> but just proves its nativity.
>
> FWIW,
>
> Maciej
>
next prev parent reply other threads:[~2026-07-08 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 21:22 [PATCH v2] x86: Start removing X86_X32_ABI 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
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 [this message]
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=20260708212628.4083e180@pumpkin \
--to=david.laight.linux@gmail.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=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=mingo@redhat.com \
--cc=neal@gompa.dev \
--cc=richard.purdie@linuxfoundation.org \
--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