From: David Laight <david.laight.linux@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, x86@kernel.org,
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 13:02:04 +0100 [thread overview]
Message-ID: <20260527130204.1f38710f@pumpkin> (raw)
In-Reply-To: <5FC3AA08-47C8-46CE-9758-20ECDE6CE018@zytor.com>
On Tue, 26 May 2026 08:54:56 -0700
"H. Peter Anvin" <hpa@zytor.com> wrote:
> On May 26, 2026 3:40:51 AM PDT, Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> >On 2026-05-23 14:43:52 [-0700], H. Peter Anvin wrote:
> >> However, we can not recycle the syscall numbers. The x32 flag in the
> >> syscall number was advisory originally; it was introduced late in the
> >> game to work around a design bug in the input subsystem (*).
> >
> >If x32 is removed/ not supported why can't the 32/64 bit ABI use syscall
> >numbers 512+? It is an ELF32 with EM_X86_64 which should be rejected.
> >Shouldn't this free the space because there are no users anymore?
> >
> >> -hpa
> >
> >Sebastian
>
> System call numbers or even mechanisms are in no wise tied to the ELF type.
> An x86-64 binary can issue x86-64, x32 or i386 system calls, even from 64-bit mode!
>
I suspect a 32bit binary can also switch to 64bit mode and issue any
of them as well.
-- David
next prev parent reply other threads:[~2026-05-27 12:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 9:37 [PATCH] x86: Start removing X86_X32_ABI 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 [this message]
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
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-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=20260527130204.1f38710f@pumpkin \
--to=david.laight.linux@gmail.com \
--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