Re: [RFC PATCH v1 0/2] genirq: add migratable NMI registration and show NMI counts

From: Ashok Raj

Date: Tue Nov 17 2026 - 20:49:17 EST


Hi Vladimir

On Mon, Nov 16, 2026 at 10:38:00AM +0000, Vladimir Murzin wrote:
> Hi Ashok,
>
> On 11/14/26 23:49, Ashok Raj wrote:
> > request_nmi() currently models NMIs as per-CPU sources. This does not
> > represent a globally routed NMI source with an affinity-capable irqchip,
> > which needs to be rerouted when its target CPU is offlined.
> >
> > This RFC adds IRQF_NMI_MIGRATABLE as a request_nmi() registration mode
> > for such a source. It remains excluded from normal IRQ balancing, but the
> > generic startup and CPU-hotplug paths may select an online target. The
> > second patch fixes the related /proc/interrupts display: NMI-safe flow
> > handling updates the per-CPU counters rather than irq_desc::tot_count.
> >
> > Patch 1: Add the migratable-NMI registration mode, validate that it is
> > used only through request_nmi() with an affinity-capable non-per-CPU
> > irqchip, and add IRQ KUnit coverage for registration and CPU-offline
> > migration.
> >
> > Patch 2: Emit the per-CPU counters for all NMI descriptors, matching
> > kstat_irqs_desc().
> >
> > Testing:
> > - ARM64 changed-object builds with WERROR=1
> > - ARM64 !SMP changed-object build
> > - ARM64 IRQ KUnit run under QEMU with two CPUs, including registration
> > validation and CPU-offline migration
> > - local downstream GHES delivery and migration validation for the intended
> > consumer topology (not part of this series)
> >
> > Base and dependencies:
> >
> > This RFC was developed and tested on v7.4-rc2 plus the FEAT_NMI v2 series
> > [1]. It depends on that series' GIC NMI support and is therefore not directly
> > applicable to mainline or linux-next as posted. This RFC is for design
> > feedback; it will need rebasing onto the upstream form of those prerequisites
> > before submission.
> >
> > [1] https://lore.kernel.org/linux-arm-kernel/20261112132042.129062-1-vladimir.murzin@xxxxxxx/
> >
>
> I'm not an expert in this area, but based on what I've learned so far,
> NMI being per-CPU like makes life much easier ;)
>
> IIUC, one of the main problems with a shared NMI (as opposed to a
> per-CPU) is handling shared state. Consider:
>
> CPU0 CPU1 CPU2
>
> ---------------------------------------------------------------------------
>
> <NMI>
> handling started
> set NMI affinity to CPU2
> <NMI>
> handling started
> mutate shared state
> mutate shared state
> handling finished
> handling finished
>
> IOW, the same NMI handler could execute concurrently on two CPUs,
> potentially corrupting shared state. Once again more than happy to
> be corrected if I missed something :)
>
Thanks, you're right, and I got it wrong in my earlier reply. genirq
doesn't serialize NMI handlers: handle_fasteoi_nmi() takes no desc->lock
and sets no IRQD_IRQ_INPROGRESS.

These interrupts are external interrupts in the platform, not Per CPU
interrupts like the perf kinds.

I'm new to the GIC, so I'd like to check an assumption. On GICv3, an
active SPI isn't signalled again until it is deactivated.
handle_fasteoi_nmi() calls chip->irq_eoi() only after the handler
returns.

So I'm assuming a second CPU can't be sent the same SPI while
the first CPU is still in the handler.

Is that a reasonable assumption?

I didn't quite follow the mutate shared state comment.

I just interpreted thast as "handler is now called in another CPU"
type assumption.

Cheers,
Ashok