[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <84be5ed882141c8b407a78590f6ecbc7080c98b0.camel@surriel.com>
Date: Fri, 07 Feb 2025 15:50:57 -0500
From: Rik van Riel <riel@...riel.com>
To: Brendan Jackman <jackmanb@...gle.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, bp@...en8.de,
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,
jannh@...gle.com, mhklinux@...look.com, andrew.cooper3@...rix.com, Manali
Shukla <Manali.Shukla@....com>
Subject: Re: [PATCH v9 06/12] x86/mm: use INVLPGB for kernel TLB flushes
On Fri, 2025-02-07 at 17:03 +0100, Brendan Jackman wrote:
> O
> With !CPU_SUP_AMD and the above, broadcast_kernel_range_flush
> disappears from tlb.o. (Caveat - I didn't actually read the disasm I
> just made it noinline and checked the call disappeared).
>
> It's actually more lines of code but now they're off in a boilerplate
> header and it's consistent with the other flags that do this.
>
What compiler did you use?
While I like the cleanup in principle, I
don't want to saddle people with older
compilers with extra code they don't need.
--
All Rights Reversed.
Powered by blists - more mailing lists