[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8734yte4xo.ffs@tglx>
Date: Mon, 02 Oct 2023 11:42:27 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Borislav Petkov <bp@...en8.de>
Cc: LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
"Chang S. Bae" <chang.seok.bae@...el.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Nikolay Borisov <nik.borisov@...e.com>
Subject: Re: [patch V3 29/30] x86/microcode: Prepare for minimal revision check
On Thu, Sep 28 2023 at 13:47, Borislav Petkov wrote:
> On Tue, Sep 12, 2023 at 09:58:30AM +0200, Thomas Gleixner wrote:
>> --- a/arch/x86/kernel/cpu/microcode/core.c
>> +++ b/arch/x86/kernel/cpu/microcode/core.c
>> @@ -46,6 +46,9 @@
>> static struct microcode_ops *microcode_ops;
>> static bool dis_ucode_ldr = true;
>>
>> +bool force_minrev = IS_ENABLED(CONFIG_MICROCODE_LATE_FORCE_MINREV);
>> +module_param(force_minrev, bool, S_IRUSR | S_IWUSR);
>
> Yeah, it's not a module anymore.
module_param is not restricted to modules. You can utilize it for
builtin code too.
Powered by blists - more mailing lists