[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231011190317.GDZSbxdd5TuCIp5+JN@fat_crate.local>
Date: Wed, 11 Oct 2023 21:03:17 +0200
From: Borislav Petkov <bp@...en8.de>
To: Josh Poimboeuf <jpoimboe@...nel.org>
Cc: Breno Leitao <leitao@...ian.org>, tglx@...utronix.de,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, leit@...a.com,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4] x86/bugs: Add a separate config for each mitigation
On Tue, Oct 10, 2023 at 09:42:52PM -0700, Josh Poimboeuf wrote:
> MITIGATION_PAGE_TABLE_ISOLATION
> MITIGATION_RETPOLINE
> MITIGATION_UNRET_ENTRY
> MITIGATION_CALL_DEPTH_TRACKING
> MITIGATION_IBPB_ENTRY
> MITIGATION_IBRS_ENTRY
> MITIGATION_SRSO
> MITIGATION_SLS
The train has already left the station on those. The other mitigations
don't have "MITIGAT*" at all in front of the name. I.e.:
config RETHUNK
config CALL_DEPTH_TRACKING
...
and prepending them all with MITIGATION_ is going to cause too much
senseless churn for a reason which I don't think is worth the effort.
So let's stick with the current naming scheme and do
config MDS
config TAA
...
and so on.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists