[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+i-1C0R7qsPgL7i1NGELLAP9weumXu8vX9x-Fo6JZbKV_=cog@mail.gmail.com>
Date: Mon, 10 Feb 2025 18:40:29 +0100
From: Brendan Jackman <jackmanb@...gle.com>
To: "Kaplan, David" <David.Kaplan@....com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...en8.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>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 10/35] x86/bugs: Restructure gds mitigation
On Mon, 10 Feb 2025 at 18:27, Kaplan, David <David.Kaplan@....com> wrote:
> On the ARCH_CAP_GDS_CTRL, I thought that check is really just to check if the MSR is present, before we try to read it.
Ah, yeah you view the conditional as saying "does that mitigation
control MSR exist" rather than making a mitigation policy decision
then I agree it makes sense.
#define ARCH_CAP_GDS_CTRL BIT(25) /*
* CPU is vulnerable to Gather
* Data Sampling (GDS) and
* has controls for mitigation.
*/
So... shrug, seems fine to me.
Powered by blists - more mailing lists