From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: mpe@ellerman.id.au, maddy@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, npiggin@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] powerpc: Enable dynamic preemption
Date: Thu, 30 Jan 2025 16:03:09 +0100 [thread overview]
Message-ID: <05f6f732-e155-4b60-8c4e-984e42e51ee4@csgroup.eu> (raw)
In-Reply-To: <20250130145409.D_so_mR1@linutronix.de>
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.
$ git grep sk_dynamic_irqentry_exit_cond_resched
arch/arm64/include/asm/preempt.h:DECLARE_STATIC_KEY_TRUE(sk_dynamic_irqentry_exit_cond_resched);
arch/arm64/kernel/entry-common.c:DEFINE_STATIC_KEY_TRUE(sk_dynamic_irqentry_exit_cond_resched);
arch/arm64/kernel/entry-common.c:
(static_branch_unlikely(&sk_dynamic_irqentry_exit_cond_resched))
include/linux/entry-common.h:DECLARE_STATIC_KEY_TRUE(sk_dynamic_irqentry_exit_cond_resched);
kernel/entry/common.c:DEFINE_STATIC_KEY_TRUE(sk_dynamic_irqentry_exit_cond_resched);
kernel/entry/common.c: if
(!static_branch_unlikely(&sk_dynamic_irqentry_exit_cond_resched))
It is in common entry but arm64 and powerpc don't use common entry.
$ git grep GENERIC_ENTRY arch
arch/Kconfig:config GENERIC_ENTRY
arch/loongarch/Kconfig: select GENERIC_ENTRY
arch/riscv/Kconfig: select GENERIC_ENTRY
arch/s390/Kconfig: select GENERIC_ENTRY
arch/x86/Kconfig: select GENERIC_ENTRY
Christophe
next prev parent reply other threads:[~2025-01-30 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 5:19 [PATCH v3 0/1] powerpc: Enable dynamic preemption Shrikanth Hegde
2025-01-06 5:19 ` [PATCH v3 1/1] " Shrikanth Hegde
2025-01-30 14:54 ` Sebastian Andrzej Siewior
2025-01-30 15:03 ` Christophe Leroy [this message]
2025-01-30 16:14 ` Sebastian Andrzej Siewior
2025-01-30 16:57 ` Shrikanth Hegde
2025-01-30 20:26 ` Sebastian Andrzej Siewior
2025-01-31 6:09 ` Christophe Leroy
2025-01-31 6:54 ` Shrikanth Hegde
2025-01-21 7:25 ` [PATCH v3 0/1] " Shrikanth Hegde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05f6f732-e155-4b60-8c4e-984e42e51ee4@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=sshegde@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).