[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250219182041.GOZ7Yg-VlXLdgX7-3Z@fat_crate.local>
Date: Wed, 19 Feb 2025 19:20:41 +0100
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>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 06/35] x86/bugs: Restructure mmio mitigation
On Wed, Feb 12, 2025 at 03:16:46PM -0800, Josh Poimboeuf wrote:
> static bool __init verw_mitigation_enabled(void)
> {
> return mds_mitigation != MDS_MITIGATION_OFF ||
> (taa_mitigation != TAA_MITIGATION_OFF && taa_vulnerable()) ||
> (mmio_mitigation != MMIO_MITIGATION_OFF && mmio_needs_verw());
> (rfds_mitigation != RFDS_MITIGATION_OFF && !rfds_needs_ucode());
> }
Instead of turning it into a head-scratching madness, it might be a lot easier
if all the places which enable VERW mitigation, would do
verw_mitigation_enabled = true;
and then the code can simply check that static var...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists