[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250130161434.0PELHkzk@linutronix.de>
Date: Thu, 30 Jan 2025 17:14:34 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: Shrikanth Hegde <sshegde@...ux.ibm.com>, mpe@...erman.id.au,
maddy@...ux.ibm.com, linuxppc-dev@...ts.ozlabs.org,
npiggin@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/1] powerpc: Enable dynamic preemption
On 2025-01-30 16:03:09 [+0100], Christophe Leroy wrote:
> Le 30/01/2025 à 15:54, Sebastian Andrzej Siewior a écrit :
> > On 2025-01-06 10:49:19 [+0530], Shrikanth Hegde wrote:
> > > --- a/arch/powerpc/kernel/interrupt.c
> > > +++ b/arch/powerpc/kernel/interrupt.c
> > > @@ -25,6 +25,10 @@
> > > unsigned long global_dbcr0[NR_CPUS];
> > > #endif
> > > +#if defined(CONFIG_PREEMPT_DYNAMIC) && defined(CONFIG_HAVE_PREEMPT_DYNAMIC_KEY)
> > > +DEFINE_STATIC_KEY_TRUE(sk_dynamic_irqentry_exit_cond_resched);
> > > +#endif
> >
> > I am uncertain here: Do you need to DEFINE it? It is set by the sched
> > core which also defines it. It should be same thing after all, right?
>
> As far as I can see it is not handled by sched core.
…
> It is in common entry but arm64 and powerpc don't use common entry.
Okay. So it is defined in the generic part (so you have to define it on
power) but it is used by sched-core (search for
preempt_dynamic_enable(irqentry_exit_cond_resched);
).
It might make sense to define it there (in the sched part where it is
used) but this is out of scope here, it just confused me :)
Thanks for the pointer.
> Christophe
Sebastian
Powered by blists - more mailing lists