[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ed8b8998a18ff5ceeaec803244897d127998ae4.camel@surriel.com>
Date: Wed, 21 May 2025 11:59:08 -0400
From: Rik van Riel <riel@...riel.com>
To: Dave Hansen <dave.hansen@...el.com>, linux-kernel@...r.kernel.org
Cc: 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, Rik van Riel <riel@...com>, Yu-cheng Yu
<yu-cheng.yu@...el.com>
Subject: Re: [RFC v2 6/9] x86/apic: Introduce Remote Action Request
Operations
On Wed, 2025-05-21 at 08:28 -0700, Dave Hansen wrote:
> > diff --git a/arch/x86/include/asm/smp.h
> > b/arch/x86/include/asm/smp.h
> > index 0c1c68039d6f..1ab9f5fcac8a 100644
> > --- a/arch/x86/include/asm/smp.h
> > +++ b/arch/x86/include/asm/smp.h
> > @@ -40,6 +40,9 @@ struct smp_ops {
> >
> > void (*send_call_func_ipi)(const struct cpumask *mask);
> > void (*send_call_func_single_ipi)(int cpu);
> > +
> > + void (*send_rar_ipi)(const struct cpumask *mask);
> > + void (*send_rar_single_ipi)(int cpu);
> > };
>
> I assume Yu-cheng did it this way.
>
> I'm curios why new smp_ops are needed for this, though. It's not like
> there are a bunch of different implementations to pick between.
>
You are right, this was in the code I received.
> I feel like this patch is doing three separate things:
>
> 1. Adds smp_ops
> 2. Refactors native_send_call_func_ipi()
> 3. Adds RAR support
>
> None of those are huge, but it would make a lot more sense to break
> those out. I'm also still not sure of the point of the smp_ops.
>
I am not very familiar with this part of the kernel,
but would be happy to make whatever changes the
maintainers want to see.
--
All Rights Reversed.
Powered by blists - more mailing lists