[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <841d88f8db26f33ede5a9277efca77e331f45e7c.camel@surriel.com>
Date: Tue, 20 May 2025 08:57:06 -0400
From: Rik van Riel <riel@...riel.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, x86@...nel.org,
kernel-team@...a.com, dave.hansen@...ux.intel.com, luto@...nel.org,
peterz@...radead.org, tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
hpa@...or.com, nadav.amit@...il.com, Yu-cheng Yu <yu-cheng.yu@...el.com>
Subject: Re: [RFC v2 7/9] x86/mm: Introduce Remote Action Request
On Tue, 2025-05-20 at 11:28 +0200, Ingo Molnar wrote:
>
> * Rik van Riel <riel@...riel.com> wrote:
>
> > From: Yu-cheng Yu <yu-cheng.yu@...el.com>
> >
> > Remote Action Request (RAR) is a TLB flushing broadcast facility.
> > To start a TLB flush, the initiator CPU creates a RAR payload and
> > sends a command to the APIC. The receiving CPUs automatically
> > flush
> > TLBs as specified in the payload without the kernel's involement.
> >
> > [ riel: add pcid parameter to smp_call_rar_many so other mms can be
> > flushed ]
>
> Please actually review & tidy up patches that you pass through, don't
> just hack them up minimally and slap your tag and SOB on top of it.
I'm happy to do that now that the code is finally working.
v3 will have much more cleanups, and hopefully a few
optimizations.
--
All Rights Reversed.
Powered by blists - more mailing lists