[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250210234413.i4vv6wuesxp37hyh@jpoimboe>
Date: Mon, 10 Feb 2025 15:44:13 -0800
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: David Kaplan <david.kaplan@....com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...en8.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,
"H . Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 09/35] x86/bugs: Restructure srbds mitigation
On Wed, Jan 08, 2025 at 02:24:49PM -0600, David Kaplan wrote:
> +static void __init srbds_apply_mitigation(void)
> +{
> + if (!boot_cpu_has_bug(X86_BUG_SRBDS))
> + return;
I realize this is just preserving the existing behavior, but for
consistency with the others this should check for cpu_mitigations_off()
so the mitigation doesn't get printed.
> update_srbds_msr();
> pr_info("%s\n", srbds_strings[srbds_mitigation]);
More generally, IMO these should be printed in the select (or update)
functions rather than in the apply functions.
--
Josh
Powered by blists - more mailing lists