From: kernel test robot <lkp@intel.com>
To: Aaron Tomlin <atomlin@atomlin.com>,
corbet@lwn.net, skhan@linuxfoundation.org
Cc: oe-kbuild-all@lists.linux.dev, tglx@kernel.org,
akpm@linux-foundation.org, bp@alien8.de, rdunlap@infradead.org,
dave.hansen@linux.intel.com, feng.tang@linux.alibaba.com,
pawan.kumar.gupta@linux.intel.com, dapeng1.mi@linux.intel.com,
kees@kernel.org, elver@google.com, paulmck@kernel.org,
lirongqing@baidu.com, bhelgaas@google.com, bigeasy@linutronix.de,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: kernel-parameters: document scope of irqaffinity= parameter
Date: Thu, 30 Apr 2026 02:28:54 +0200 [thread overview]
Message-ID: <202604300215.1Alrqyxi-lkp@intel.com> (raw)
In-Reply-To: <20260421150911.42404-1-atomlin@atomlin.com>
Hi Aaron,
kernel test robot noticed the following build warnings:
[auto build test WARNING on lwn/docs-next]
[also build test WARNING on linus/master v7.1-rc1 next-20260429]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Aaron-Tomlin/docs-kernel-parameters-document-scope-of-irqaffinity-parameter/20260423-221944
base: git://git.lwn.net/linux.git docs-next
patch link: https://lore.kernel.org/r/20260421150911.42404-1-atomlin%40atomlin.com
patch subject: [PATCH v2] docs: kernel-parameters: document scope of irqaffinity= parameter
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
reproduce: (https://download.01.org/0day-ci/archive/20260430/202604300215.1Alrqyxi-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202604300215.1Alrqyxi-lkp@intel.com/
All warnings (new ones prefixed by >>):
Warning: tools/docs/documentation-file-ref-check references a file that doesn't exist: Documentation/devicetree/dt-object-internal.txt
Warning: tools/docs/documentation-file-ref-check references a file that doesn't exist: m,^Documentation/scheduler/sched-pelt
Warning: tools/docs/documentation-file-ref-check references a file that doesn't exist: m,(Documentation/translations/[
Using alabaster theme
Documentation/core-api/irq/managed_irq.rst:97: ERROR: Unexpected indentation. [docutils]
>> Documentation/core-api/irq/managed_irq.rst:104: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/core-api/irq/managed_irq.rst:109: ERROR: Unexpected indentation. [docutils]
Documentation/core-api/irq/managed_irq.rst:111: ERROR: Unexpected indentation. [docutils]
Documentation/core-api/irq/managed_irq.rst:118: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/core-api/irq/managed_irq.rst:122: ERROR: Unexpected indentation. [docutils]
Documentation/core-api/irq/managed_irq.rst:123: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
vim +104 Documentation/core-api/irq/managed_irq.rst
65
66 - A QEMU instance is booted with "-device virtio-scsi-pci".
67 The MSI‑X device exposes 11 interrupts: 3 "management" interrupts and 8
68 "queue" interrupts. The driver requests the 8 queue interrupts, each of which
69 is affine to exactly one CPU. If that CPU goes offline, the interrupt is shut
70 down.
71
72 Assuming interrupt 48 is one of the queue interrupts, the following appears::
73
74 /proc/irq/48/effective_affinity_list:7
75 /proc/irq/48/smp_affinity_list:7
76
77 This indicates that the interrupt is served only by CPU7. Shutting down CPU7
78 does not migrate the interrupt to another CPU::
79
80 /proc/irq/48/effective_affinity_list:0
81 /proc/irq/48/smp_affinity_list:7
82
83 If the Linux kernel was built with Kconfig CONFIG_GENERIC_IRQ_DEBUGFS
84 enabled, this can be verified via the debugfs interface (e.g.,
85 /sys/kernel/debug/irq/irqs/48). The dstate field will include
86 IRQD_IRQ_DISABLED, IRQD_IRQ_MASKED and IRQD_MANAGED_SHUTDOWN.
87 A managed IRQ will also include IRQD_AFFINITY_MANAGED. For example:
88
89 # cat /sys/kernel/debug/irq/irqs/87
90 handler: handle_edge_irq
91 device: 0000:41:00.0
92 status: 0x00000000
93 istate: 0x00004000
94 ddepth: 0
95 wdepth: 0
96 dstate: 0x19601200
97 IRQD_ACTIVATED
98 IRQD_IRQ_STARTED
99 IRQD_SINGLE_TARGET
100 IRQD_AFFINITY_SET
101 IRQD_AFFINITY_MANAGED
102 IRQD_AFFINITY_ON_ACTIVATE
103 IRQD_HANDLE_ENFORCE_IRQCTX
> 104 node: 0
105 affinity: 9
106 effectiv: 9
107 pending:
108 domain: IR-PCI-MSIX-0000:41:00.0-12
109 hwirq: 0x8
110 chip: IR-PCI-MSIX-0000:41:00.0
111 flags: 0x430
112 IRQCHIP_SKIP_SET_WAKE
113 IRQCHIP_ONESHOT_SAFE
114
115 address_hi: 0x00000000
116 address_lo: 0xfee00000
117 msg_data: 0x00000008
118 parent:
119 domain: AMD-IR-3-14
120 hwirq: 0x41000000
121 chip: AMD-IR
122 flags: 0x0
123 parent:
124 domain: VECTOR
125 hwirq: 0x57
126 chip: APIC
127 flags: 0x0
128 Vector: 33
129 Target: 9
130 move_in_progress: 0
131 is_managed: 1
132 can_reserve: 0
133 has_reserved: 0
134 cleanup_pending: 0
135
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-04-30 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 15:09 [PATCH v2] docs: kernel-parameters: document scope of irqaffinity= parameter Aaron Tomlin
2026-04-30 0:28 ` kernel test robot [this message]
2026-04-30 7:08 ` Bagas Sanjaya
2026-05-03 15:16 ` Jonathan Corbet
2026-05-03 15:41 ` Aaron Tomlin
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=202604300215.1Alrqyxi-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=bhelgaas@google.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dapeng1.mi@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=elver@google.com \
--cc=feng.tang@linux.alibaba.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--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