[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87352shc98.fsf@linux.intel.com>
Date: Thu, 15 Jun 2023 10:21:55 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Breno Leitao <leitao@...ian.org>
Cc: pawan.kumar.gupta@...ux.intel.com, jpoimboe@...nel.org,
peterz@...radead.org, tglx@...utronix.de, bp@...en8.de,
leit@...com, hpa@...or.com, x86@...nel.org, mingo@...hat.com,
dave.hansen@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] x86/bugs: Break down mitigations configurations
Breno Leitao <leitao@...ian.org> writes:
> There is no way to compile a kernel today with some of the speculative
> mitigations disabled. Even if the kernel has
> CONFIG_SPECULATION_MITIGATIONS=n, some Intel mitigations, such as MDS, TAA,
> MMIO are still enabled and can only be disabled using a kernel parameter.
>
> This patchset creates a way to choose what to enable or disable, and,
> get the mitigations disable if CONFIG_SPECULATION_MITIGATIONS is not
> set, as the rest of other mitigations.
>
> Also, we want to print a warning message letting users know that these
> mitigations are disabled.
>
> This is a follow up to this discussion: https://lkml.org/lkml/2023/6/12/798
>
Isn't this all roughly equivalent to CONFIG_CMDLINE="mitigations=..." ?
-Andi
Powered by blists - more mailing lists