[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251103182453.GPaQjzdVCYTKRb7H5Y@fat_crate.local>
Date: Mon, 3 Nov 2025 19:24:53 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Kaplan, David" <David.Kaplan@....com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...nel.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 04/56] x86/bugs: Reset spectre_v1 mitigations
On Wed, Oct 29, 2025 at 01:48:03PM +0000, Kaplan, David wrote:
> We have cross-dependencies around the *selection* of mitigations, but not
> around the application of them. There is no ordering requirement around the
> *_apply_mitigation() functions. As such I would not expect (and have not
> observed) any ordering requirements around the reset functions.
This sounds like a single undo-function should be fine...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists