Re: [PATCH v2] docs: kernel-parameters: document scope of irqaffinity= parameter

From: Aaron Tomlin

Date: Sun May 03 2026 - 11:41:21 EST


On Sun, May 03, 2026 at 09:16:01AM -0600, Jonathan Corbet wrote:
> > diff --git a/Documentation/core-api/irq/managed_irq.rst b/Documentation/core-api/irq/managed_irq.rst
> > index 05e295f3c289..8e973a7d1bd1 100644
> > --- a/Documentation/core-api/irq/managed_irq.rst
> > +++ b/Documentation/core-api/irq/managed_irq.rst
> > @@ -80,9 +80,58 @@ The following examples assume a system with 8 CPUs.
> > /proc/irq/48/effective_affinity_list:0
> > /proc/irq/48/smp_affinity_list:7
> >
> > - This can be verified via the debugfs interface
> > - (/sys/kernel/debug/irq/irqs/48). The dstate field will include
> > + If the Linux kernel was built with Kconfig CONFIG_GENERIC_IRQ_DEBUGFS
> > + enabled, this can be verified via the debugfs interface (e.g.,
> > + /sys/kernel/debug/irq/irqs/48). The dstate field will include
> > IRQD_IRQ_DISABLED, IRQD_IRQ_MASKED and IRQD_MANAGED_SHUTDOWN.
> > + A managed IRQ will also include IRQD_AFFINITY_MANAGED. For example:
> > +
> > + # cat /sys/kernel/debug/irq/irqs/87
> > + handler: handle_edge_irq
> > + device: 0000:41:00.0
>
> This will not render the way you seem to expect, it should be a literal
> block. Please do build the docs and look at the results before sending
> documentation patches.
>
Hi Jon,

Acknowledged. I'll resolve the above in the next iteration.


Kind regards,
--
Aaron Tomlin

Attachment: signature.asc
Description: PGP signature