[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251017163644.GGaPJwnNnZUHIlL3KF@fat_crate.local>
Date: Fri, 17 Oct 2025 18:36:44 +0200
From: Borislav Petkov <bp@...en8.de>
To: Josh Poimboeuf <jpoimboe@...nel.org>
Cc: "Kaplan, David" <David.Kaplan@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>,
"H . Peter Anvin" <hpa@...or.com>, Alexander Graf <graf@...zon.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 03/56] cpu: Reset global mitigations
On Fri, Oct 17, 2025 at 09:03:08AM -0700, Josh Poimboeuf wrote:
> I'd say generic is probably the way to go, as the sysfs files and
> mitigations= interfaces are already generic, and users might want this
> on other arches eventually.
Then users will do the move then. What's the point of making some Kconfig glue
generic if there's no other-arch implementation in the works?
And if other arch does that, they can do those minor Kconfig modifications
then. We don't do "someone might want this" code design anyway...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists