From: David Laight <david.laight.linux@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
"Ahmed S . Darwish" <darwi@linutronix.de>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
John Ogness <john.ogness@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH -v3 0/15] x86: Remove support for TSC-less and CX8-less CPUs
Date: Sun, 14 Dec 2025 13:39:25 +0000 [thread overview]
Message-ID: <20251214133925.1e80f851@pumpkin> (raw)
In-Reply-To: <20251214084710.3606385-1-mingo@kernel.org>
On Sun, 14 Dec 2025 09:46:48 +0100
Ingo Molnar <mingo@kernel.org> wrote:
>...
>
> Original -v1 announcement:
>
> In the x86 architecture we have various complicated hardware emulation
> facilities on x86-32 to support ancient 32-bit CPUs that very very few
> people are using with modern kernels. This compatibility glue is sometimes
> even causing problems that people spend time to resolve, which time could
> be spent on other things.
>
> As Linus recently remarked:
>
> > I really get the feeling that it's time to leave i486 support behind.
> > There's zero real reason for anybody to waste one second of
> > development effort on this kind of issue.
>
> This series increases minimum kernel support features to include TSC and
> CX8 (CMPXCHG8B) hardware support, which removes 486 (and derivatives) support
> and early-586 (and derivatives) support.
Two questions:
1) What happens if you try to boot the kernel on an old system?
Is there an early check that makes it fail 'moderately gracefully'?
2) Is it worth also dropping support for cpu that don't support CMOV.
I think that is 'Pentium Pro' and 'K7' rather than 'Pentium' and 'K5'.
That simplifies some asm code.
'masked' user access would really need it (and a guard page).
The 'long nop' get added at the same time.
It is also (almost certainly) new enough that the 'bit scan' instructions
are guaranteed to leave the the destination unchanged if the source is
zero (dropping just 486 may be enough for that).
Moving the minimum cpu to P-Pro now will probably save another similar
change in the near future.
David
next prev parent reply other threads:[~2025-12-14 13:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 8:46 [PATCH -v3 0/15] x86: Remove support for TSC-less and CX8-less CPUs Ingo Molnar
2025-12-14 8:46 ` [PATCH 01/15] x86/cpu: Remove M486/M486SX/ELAN support Ingo Molnar
2026-03-30 7:05 ` [tip: x86/platform] " tip-bot2 for Ingo Molnar
2026-03-30 9:45 ` tip-bot2 for Ingo Molnar
2025-12-14 8:46 ` [PATCH 02/15] x86/cpu: Remove CONFIG_MWINCHIP3D/MWINCHIPC6 Ingo Molnar
2025-12-14 8:46 ` [PATCH 03/15] x86/cpu: Remove CPU_SUP_UMC_32 support Ingo Molnar
2025-12-14 8:46 ` [PATCH 04/15] x86/cpu: Remove TSC-less CONFIG_M586 support Ingo Molnar
2025-12-14 8:46 ` [PATCH 05/15] x86/cpu, x86/platform, watchdog: Remove CONFIG_X86_RDC321X support Ingo Molnar
2025-12-14 8:46 ` [PATCH 06/15] x86/cpu: Remove the CONFIG_X86_INVD_BUG quirk Ingo Molnar
2025-12-14 8:46 ` [PATCH 07/15] x86/cpu, cpufreq: Remove AMD ELAN support Ingo Molnar
2025-12-14 8:46 ` [PATCH 08/15] x86/fpu: Remove MATH_EMULATION and related glue code Ingo Molnar
2025-12-14 8:46 ` [PATCH 09/15] x86/fpu: Remove the 'no387' boot option Ingo Molnar
2025-12-14 8:46 ` [PATCH 10/15] x86/fpu: Remove the math-emu/ FPU emulation library Ingo Molnar
2025-12-14 8:46 ` [PATCH 11/15] x86/cpu: Make CONFIG_X86_TSC unconditional Ingo Molnar
2025-12-14 8:47 ` [PATCH 12/15] x86: Remove !CONFIG_X86_TSC code Ingo Molnar
2025-12-14 8:47 ` [PATCH 13/15] x86/cpu: Make CONFIG_X86_CX8 unconditional Ingo Molnar
2025-12-14 8:47 ` [PATCH 14/15] x86/atomics: Remove !CONFIG_X86_CX8 methods Ingo Molnar
2025-12-14 8:47 ` [PATCH 15/15] x86/percpu: " Ingo Molnar
2025-12-14 9:38 ` Uros Bizjak
2025-12-15 7:05 ` [PATCH 15/15 -v4] " Ingo Molnar
2025-12-14 13:39 ` David Laight [this message]
2025-12-15 4:22 ` [PATCH -v3 0/15] x86: Remove support for TSC-less and CX8-less CPUs H. Peter Anvin
2025-12-15 2:39 ` Brian Gerst
2025-12-15 3:19 ` Linus Torvalds
2025-12-15 13:55 ` Ahmed S. Darwish
2026-01-04 13:08 ` Borislav Petkov
2026-01-07 3:57 ` H. Peter Anvin
2025-12-15 15:54 ` Arnd Bergmann
2026-01-03 22:59 ` Maciej W. Rozycki
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=20251214133925.1e80f851@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=ardb@kernel.org \
--cc=arnd@kernel.org \
--cc=bp@alien8.de \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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