All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] x86: Start removing X86_X32_ABI
Date: Thu, 04 Jun 2026 22:27:28 +0200	[thread overview]
Message-ID: <87o6hq3vbj.ffs@fw13> (raw)
In-Reply-To: <10BF3F18-4709-43D6-979C-49067707F1C1@zytor.com>

On Sat, May 23 2026 at 14:43, H. Peter Anvin wrote:
> On May 23, 2026 2:37:34 AM PDT, Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>>-
>> config COMPAT_32
>> 	def_bool y
>> 	depends on IA32_EMULATION || X86_32
>
> So I'm not opposed to sunsetting x32; it happened too late to actually
> be able to become useful (sorry, Knuth.)

I doubt it was ever useful, but that's a different debate to be had.

> 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 (*).

Correct. That's unfortunate and basically forces us to skip the
arbitrary x32 range for all architectures if we want to keep the syscall
numbers in sync.

But aside of that x32 is just another maintenance burden for no value.

Please let us get rid of it and document that the syscall number space
is poisened forever.

Thanks,

        tglx

  parent reply	other threads:[~2026-06-04 20:27 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
2026-06-01 21:29         ` H. Peter Anvin
2026-06-04 20:27   ` Thomas Gleixner [this message]
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=87o6hq3vbj.ffs@fw13 \
    --to=tglx@kernel.org \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.