mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Radu Rendec <radu@rendec.net>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Thomas Gleixner <tglx@kernel.org>
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] parisc: Remove unnecessary NULL check of the kstat_irqs field
Date: Sat, 25 Jul 2026 22:04:20 +0200	[thread overview]
Message-ID: <2edb44c9-46d0-4f98-9588-339220ad3c74@gmx.de> (raw)
In-Reply-To: <20260705210951.2717741-3-radu@rendec.net>

On 7/5/26 23:09, Radu Rendec wrote:
> The kstat_irqs field of struct irq_desc is used to store a per-cpu count
> of interrupt events. It is initialized in init_desc(), along with all
> the other fields in struct irq_desc that need explicit initialization,
> and therefore it's always available (non-NULL) for any valid interrupt
> descriptor.
> 
> On parisc, CONFIG_SPARSE_IRQ is disabled, interrupt descriptors are
> allocated statically in the irq_desc[] array, and kstat_irqs is
> initialized implicitly to NULL. The kstat_irqs field is initialized
> later, for all descriptors, via start_kernel() -> early_irq_init() ->
> init_desc().
> 
> smp_boot_one_cpu() is used only for CPU hotplugging. On a SMP system,
> the boot CPU initializes the interrupt descriptors as described above,
> and smp_boot_one_cpu() is called later, for the secondary CPU(s).
> 
> The previous patch in this series makes a similar change across the
> generic IRQ code in kernel/irq/irqdesc.c, and provides a more detailed
> explanation of why kstat_irqs is guaranteed to be non-NULL.
> 
> Signed-off-by: Radu Rendec <radu@rendec.net>
> ---
>   arch/parisc/kernel/smp.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)

Acked-by: Helge Deller <deller@gmx.de>


      parent reply	other threads:[~2026-07-25 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 21:09 [PATCH 0/2] " Radu Rendec
2026-07-05 21:09 ` [PATCH 1/2] genirq: " Radu Rendec
2026-07-07 19:39   ` [tip: irq/core] " tip-bot2 for Radu Rendec
2026-07-05 21:09 ` [PATCH 2/2] parisc: " Radu Rendec
2026-07-07 19:38   ` [tip: irq/core] " tip-bot2 for Radu Rendec
2026-07-25 20:04   ` Helge Deller [this message]

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=2edb44c9-46d0-4f98-9588-339220ad3c74@gmx.de \
    --to=deller@gmx.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=radu@rendec.net \
    --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

all inboxes | Powered by JetHome®