[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230603163751.GBZHtsXwW5UUnsSbKX@fat_crate.local>
Date: Sat, 3 Jun 2023 18:37:51 +0200
From: Borislav Petkov <bp@...en8.de>
To: "Chang S. Bae" <chang.seok.bae@...el.com>
Cc: linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
dm-devel@...hat.com, ebiggers@...nel.org, elliott@....com,
gmazyland@...il.com, luto@...nel.org, dave.hansen@...ux.intel.com,
tglx@...utronix.de, mingo@...nel.org, x86@...nel.org,
herbert@...dor.apana.org.au, ardb@...nel.org,
dan.j.williams@...el.com, bernie.keany@...el.com,
charishma1.gairuboyina@...el.com,
lalithambika.krishnakumar@...el.com, nhuck@...gle.com,
Jonathan Corbet <corbet@....net>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-doc@...r.kernel.org
Subject: Re: [PATCH v8 09/12] x86/cpu: Add a configuration and command line
option for Key Locker
On Sat, Jun 03, 2023 at 08:22:24AM -0700, Chang S. Bae wrote:
> +static __init int x86_nokeylocker_setup(char *arg)
> +{
> + /* Expect an exact match without trailing characters. */
> + if (strlen(arg))
> + return 0;
> +
> + if (!cpu_feature_enabled(X86_FEATURE_KEYLOCKER))
> + return 1;
> +
> + setup_clear_cpu_cap(X86_FEATURE_KEYLOCKER);
> + pr_info("x86/keylocker: Disabled by kernel command line.\n");
> + return 1;
> +}
> +__setup("nokeylocker", x86_nokeylocker_setup);
Can we stop adding those just to remove them at some point later but
simply do:
clearcpuid=keylocker
?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists