From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Shrikanth Hegde <sshegde@linux.ibm.com>,
maddy@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
tglx@kernel.org
Cc: christophe.leroy@csgroup.eu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] powerpc/irq: Move __softirq_pending out of irq_stat
Date: Fri, 29 May 2026 09:43:13 +0200 [thread overview]
Message-ID: <68c83e4d-92e8-4471-99b2-404eb4f79ffa@kernel.org> (raw)
In-Reply-To: <20260523174016.999456-2-sshegde@linux.ibm.com>
Le 23/05/2026 à 19:40, Shrikanth Hegde a écrit :
> __softirq_pending isn't part of arch specific irq_stats. It is used
> by softirq core for various decision making such as whether to kick off
> ksoftirqd.
>
> Move it out of irq_cpustat_t. This makes it simple to make irq_cpustat_t
> array based approach.
Some reference to commit 0fd7d8628529 ("softirq/core: Consolidate
default local_softirq_pending() implementations") should be made I think
for better understanding.
>
> Signed-off-by: Shrikanth Hegde <sshegde@linux.ibm.com>
Reviewed-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
> ---
> arch/powerpc/include/asm/hardirq.h | 3 ++-
> arch/powerpc/kernel/irq.c | 1 +
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/include/asm/hardirq.h b/arch/powerpc/include/asm/hardirq.h
> index f133b5930ae1..bf3926a0c69c 100644
> --- a/arch/powerpc/include/asm/hardirq.h
> +++ b/arch/powerpc/include/asm/hardirq.h
> @@ -6,7 +6,6 @@
> #include <linux/irq.h>
>
> typedef struct {
> - unsigned int __softirq_pending;
> unsigned int timer_irqs_event;
> unsigned int broadcast_irqs_event;
> unsigned int timer_irqs_others;
> @@ -23,6 +22,8 @@ typedef struct {
> } ____cacheline_aligned irq_cpustat_t;
>
> DECLARE_PER_CPU_SHARED_ALIGNED(irq_cpustat_t, irq_stat);
> +DECLARE_PER_CPU(unsigned int, __softirq_pending);
> +#define local_softirq_pending_ref __softirq_pending
>
> #define __ARCH_IRQ_STAT
> #define __ARCH_IRQ_EXIT_IRQS_DISABLED
> diff --git a/arch/powerpc/kernel/irq.c b/arch/powerpc/kernel/irq.c
> index a0e8b998c9b5..f33df5e5c23f 100644
> --- a/arch/powerpc/kernel/irq.c
> +++ b/arch/powerpc/kernel/irq.c
> @@ -73,6 +73,7 @@
>
> DEFINE_PER_CPU_SHARED_ALIGNED(irq_cpustat_t, irq_stat);
> EXPORT_PER_CPU_SYMBOL(irq_stat);
> +DEFINE_PER_CPU(unsigned int, __softirq_pending);
>
> #ifdef CONFIG_PPC32
> atomic_t ppc_n_lost_interrupts;
next prev parent reply other threads:[~2026-05-29 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 17:40 [PATCH 0/3] powerpc/irq: Use optimizations for /proc/interrupts Shrikanth Hegde
2026-05-23 17:40 ` [PATCH 1/3] powerpc/irq: Move __softirq_pending out of irq_stat Shrikanth Hegde
2026-05-29 7:43 ` Christophe Leroy (CS GROUP) [this message]
2026-05-23 17:40 ` [PATCH 2/3] powerpc/irq: Make irqstats array based Shrikanth Hegde
2026-05-29 7:46 ` Christophe Leroy (CS GROUP)
2026-05-23 17:40 ` [PATCH 3/3] powerpc/irq: Suppress unlikely interrupt stats by default Shrikanth Hegde
2026-05-29 7:51 ` Christophe Leroy (CS GROUP)
2026-05-29 8:09 ` 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=68c83e4d-92e8-4471-99b2-404eb4f79ffa@kernel.org \
--to=chleroy@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=tglx@kernel.org \
/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