[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1f687692160c4c4574588fd2815ab912892ed10c.camel@surriel.com>
Date: Wed, 05 Feb 2025 09:52:22 -0500
From: Rik van Riel <riel@...riel.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, bp@...en8.de,
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>, David.Kaplan@....com
Subject: Re: [PATCH v8 10/12] x86/mm: do targeted broadcast flushing from
tlbbatch code
On Wed, 2025-02-05 at 14:51 +0100, Peter Zijlstra wrote:
>
> How about we do something like this instead?
>
> This keeps all the TLBSYNC in the same task as the INVLPGB, without
> making things complicated and allowing random CR3 writes in between
> them -- which makes my head hurt.
I like your idea better!
Guess I should go make and test a v9 with
the WARN_ONCE in patch 3, and these changes :)
--
All Rights Reversed.
Powered by blists - more mailing lists