[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+i-1C2nPV9Q=baw8NJN8rt7TuTcCaA+JpdJMpVNsOqjLk3=vQ@mail.gmail.com>
Date: Thu, 13 Feb 2025 19:38:56 +0100
From: Brendan Jackman <jackmanb@...gle.com>
To: Rik van Riel <riel@...riel.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
Subject: Re: [PATCH v11 00/12] AMD broadcast TLB invalidation
On Thu, 13 Feb 2025 at 19:31, Brendan Jackman <jackmanb@...gle.com> wrote:
>
> On Thu, 13 Feb 2025 at 17:20, Rik van Riel <riel@...riel.com> wrote:
> >
> > Add support for broadcast TLB invalidation using AMD's INVLPGB instruction.
>
> Oh - what if the user sets nopcid. We need to disable invlpgb in that
> case right?
>
> (I assume it could be made to work, but doesn't seem like a case worth
> optimising).
BTW there are still a couple of unresolved threads from previous versions.
KPTI comment:
https://lore.kernel.org/linux-kernel/CA+i-1C2zuctxx6oPVVu0zBJ=Q=Hs73mgrWs5jsp8obARNcUS9g@mail.gmail.com/
and
https://lore.kernel.org/linux-kernel/20250212104239.GF19118@noisy.programming.kicks-ass.net/
Clarify context-switch sync:
https://lore.kernel.org/linux-kernel/CA+i-1C2CcQmrbdv0wLUJFD6m85D7LekejU=VdgMxnqZW=DRPxA@mail.gmail.com/
(there's another mention of it somewhere that I can't find)
Suggestion for WARN_ON_ONCE:
https://lore.kernel.org/linux-kernel/CA+i-1C3-F-VAy_JccwKx_AcD1mXsVcGHGwUFvi_ruAiqusiXZQ@mail.gmail.com/
Powered by blists - more mailing lists