[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250220102352.GBZ7cCuGd_hy-OaHlK@fat_crate.local>
Date: Thu, 20 Feb 2025 11:23:52 +0100
From: Borislav Petkov <bp@...en8.de>
To: Rik van Riel <riel@...riel.com>
Cc: Dave Hansen <dave.hansen@...el.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, peterz@...radead.org,
dave.hansen@...ux.intel.com, zhengqi.arch@...edance.com,
nadav.amit@...il.com, thomas.lendacky@....com, kernel-team@...a.com,
linux-mm@...ck.org, akpm@...ux-foundation.org, jackmanb@...gle.com,
jannh@...gle.com, mhklinux@...look.com, andrew.cooper3@...rix.com,
Manali Shukla <Manali.Shukla@....com>
Subject: Re: [PATCH v11 05/12] x86/mm: add INVLPGB support code
On Wed, Feb 19, 2025 at 09:49:01PM -0500, Rik van Riel wrote:
> I'll re-do the series without ifdefs, except for
> the one masking out X86_FEATURE_INVLPGB (on 32
> bit systems).
>
> Then the compiler should be able to get rid of
> the other code, when the feature is hard-disabled.
Thanks.
In talking to Dave last night, I think we are fine with having the majority of
ifdeffery in headers and keep it away from .c files.
Any new Kconfig symbol adds more configurations we must build and test but...
oh well.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists