[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac406e2cc2daaed5856df0af787bf21597b95f5c.camel@surriel.com>
Date: Wed, 19 Feb 2025 21:49:01 -0500
From: Rik van Riel <riel@...riel.com>
To: Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...el.com>
Cc: 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, 2025-02-19 at 20:15 +0100, Borislav Petkov wrote:
> On Wed, Feb 19, 2025 at 11:01:17AM -0800, Dave Hansen wrote:
> > But, either way, #ifdefs are a sign of weakness. Less so in a
> > header and
> > more so in a .c file.
>
> ... and, as we just discussed and agreed on chat, we don't need the
> Kconfig
> option either.
>
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.
--
All Rights Reversed.
Powered by blists - more mailing lists