mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	kernel test robot <oliver.sang@intel.com>,
	oe-lkp@lists.linux.dev, kernel test robot <lkp@intel.com>,
	linux-kernel@vger.kernel.org, John Stultz <jstultz@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Stephen Boyd <sboyd@kernel.org>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC PATCH 0/15] x86: Remove support for TSC-less and CX8-less CPUs
Date: Fri, 25 Apr 2025 09:40:46 +0200	[thread overview]
Message-ID: <aAs8fuPmXz7kK1l4@gmail.com> (raw)
In-Reply-To: <dd29df0c-0b4f-44e6-b71b-2a358ea76fb4@app.fastmail.com>


* Arnd Bergmann <arnd@arndb.de> wrote:

> >       x86/platform: Remove CONFIG_X86_RDC321X support
> >       arch/x86, gpio: Remove GPIO_RDC321X support
> >       arch/x86, watchdog: Remove the RDC321X_WDT watchdog driver
> >       arch/x86, mfd: Remove MFD_RDC321X support
> >       x86/reboot: Remove the RDC321X reboot quirk
> 
> I'm not sure about the RDC321X bits. Obviously the original
> 321x/861x/vortex86sx chips are obsolete and can be removed,
> but the product line is still actively developed by RDC and 
> DM&P, and I suspect that some of the drivers are still used
> on 586tsc-class (vortex86dx, vortex86mx) and 686-class
> (vortex86dx3, vortex86ex) SoCs that do run modern kernels and
> get updates.

So CONFIG_X86_RDC321X actively selects M486:

+++ b/arch/x86/Kconfig
 
 config X86_RDC321X
        bool "RDC R-321x SoC"
        depends on X86_32
        depends on X86_EXTENDED_PLATFORM
        select M486
        ^^^^^^^^^^^
        select X86_REBOOTFIXUPS

But indeed the other drivers are not dependent on M486, at least 
overtly:

  arch/x86, mfd: Remove MFD_RDC321X support
  arch/x86, watchdog: Remove the RDC321X_WDT watchdog driver
  arch/x86, gpio: Remove GPIO_RDC321X support

Although the watchdog driver has this indirect dependency:

   drivers/watchdog/Kconfig:       depends on X86_RDC321X || COMPILE_TEST

But the 486 kernel would work on any 586/686 upgraded boards as well.

Anyway, I've dropped the mfd/watchdog/gpio removal patches, no harm in 
keeping these drivers, and I've switched the watchdog driver over to 
X86_32:

  config RDC321X_WDT
        tristate "RDC R-321x SoC watchdog"
        depends on X86_32 || COMPILE_TEST

There's also no harm in keeping the southbridge reboot quirk I suppose, 
so I've dropped this as well:

  x86/reboot: Remove the RDC321X reboot quirk


> >       x86/cpu: Remove CPU_SUP_UMC_32 support
> >       x86/cpu: Remove TSC-less CONFIG_M586 support
> 
> I think Winchip6 (486-class, no tsc, no cx8) and Winchip3D
> (486-class, with tsc but no cx8) need to go as well then.

Okay, agreed, I've added this patch to the tree:

  bf82539ad9f6 x86/cpu: Remove CONFIG_MWINCHIP3D/MWINCHIPC6

  arch/x86/Kconfig.cpu            | 28 ++++------------------------
  arch/x86/Makefile_32.cpu        |  2 --
  arch/x86/include/asm/vermagic.h |  4 ----
  3 files changed, 4 insertions(+), 30 deletions(-)

> At this point, maybe we can consider removing CONFIG_X86_GENERIC and 
> just always build kernels that work across a wide set of CPUs: Only 
> CMOV and PAE still require a CPU with the hardware support, and 
> X86_L1_CACHE_SHIFT needs to be at least 6 (64 byte) for 
> compatibility, but everything else should just be a tuning option.

Agreed.

Thanks,

	Ingo

  reply	other threads:[~2025-04-25  7:40 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21  8:12 [linus:master] [x86/cpu] f388f60ca9: BUG:soft_lockup-CPU##stuck_for#s![swapper:#] kernel test robot
2025-04-22 10:16 ` Arnd Bergmann
2025-04-24  2:12   ` Oliver Sang
2025-04-24  7:59     ` Arnd Bergmann
2025-04-24 16:07       ` Linus Torvalds
2025-04-24 17:54         ` [RFC PATCH 0/15] x86: Remove support for TSC-less and CX8-less CPUs Ingo Molnar
2025-04-24 18:01           ` Ingo Molnar
2025-04-24 21:27           ` Arnd Bergmann
2025-04-25  7:40             ` Ingo Molnar [this message]
2025-04-25  9:30               ` Arnd Bergmann
2025-04-26  4:06         ` [linus:master] [x86/cpu] f388f60ca9: BUG:soft_lockup-CPU##stuck_for#s![swapper:#] H. Peter Anvin
2025-04-27  5:48       ` Oliver Sang
2025-04-27 12:07         ` Arnd Bergmann
2025-04-27 16:39         ` Linus Torvalds
2025-04-27 21:19           ` H. Peter Anvin
2025-04-25  8:41 [RFC PATCH 0/15] x86: Remove support for TSC-less and CX8-less CPUs Ingo Molnar
2025-04-25 11:13 ` Arnd Bergmann
2025-04-26  8:26 ` Pavel Machek
2025-05-05  8:53 ` Maciej W. Rozycki
2025-05-05 12:48   ` H. Peter Anvin
2025-05-05 13:04     ` Maciej W. Rozycki
2025-05-05 19:57       ` H. Peter Anvin
2025-05-05 20:54         ` Borislav Petkov
2025-05-06 13:51           ` Maciej W. Rozycki
2025-05-06 14:16             ` Borislav Petkov
2025-05-08 14:51               ` Maciej W. Rozycki
2025-05-08 20:11                 ` Borislav Petkov
2025-05-12 12:55                   ` Maciej W. Rozycki
2025-05-12 13:48                     ` Borislav Petkov
2025-05-12 17:29                       ` Maciej W. Rozycki
2025-05-13  2:00                         ` Linus Torvalds
2025-05-13  3:48                           ` H. Peter Anvin
2025-05-13  5:43                           ` John Paul Adrian Glaubitz
2025-05-13 21:55                             ` Maciej W. Rozycki
2025-05-13 22:02                               ` Linus Torvalds
2025-05-13 22:06                                 ` H. Peter Anvin
2025-05-15 16:32                                 ` Maciej W. Rozycki
2025-05-06 13:48         ` Maciej W. Rozycki
2025-05-06 13:54           ` John Paul Adrian Glaubitz
2025-05-05 15:59   ` Linus Torvalds
2025-05-06 13:53     ` Maciej W. Rozycki
2025-05-06 16:44       ` H. Peter Anvin
2025-05-06 17:11         ` Linus Torvalds
2025-05-06 17:51           ` H. Peter Anvin
2025-05-08 14:54             ` Maciej W. Rozycki
2025-05-08 14:53           ` Maciej W. Rozycki
2025-05-08 14:51         ` 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=aAs8fuPmXz7kK1l4@gmail.com \
    --to=mingo@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=peterz@infradead.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

Powered by JetHome