[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DDJQYGOJ4VTT.20JIC6NWZXUYW@google.com>
Date: Thu, 16 Oct 2025 12:31:38 +0000
From: Brendan Jackman <jackmanb@...gle.com>
To: David Kaplan <david.kaplan@....com>, 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>,
"H . Peter Anvin" <hpa@...or.com>
Cc: Alexander Graf <graf@...zon.com>, Boris Ostrovsky <boris.ostrovsky@...cle.com>,
<linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 20/56] x86/bugs: Move bugs.c logic out of .init section
On Mon Oct 13, 2025 at 2:34 PM UTC, David Kaplan wrote:
> If dynamic mitigations are supported, all the mitigation selection
> functions and mitigation choices may change at runtime. Therefore, none of
> the functions may exist in .init and the data must not be read-only.
I suppose we should have something akin to
__meminit/__init_or_module/__net_init here (like __init, but conditional
on Kconfig), so that users with CONFIG_DYNAMIC_MITIGATIONS=n can still
get the RAM back?
Powered by blists - more mailing lists