From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Aaron Tomlin <atomlin@atomlin.com>,
corbet@lwn.net, skhan@linuxfoundation.org
Cc: 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 14:08:48 +0700 [thread overview]
Message-ID: <afMAAL4lB72HiSQI@archie.me> (raw)
In-Reply-To: <20260421150911.42404-1-atomlin@atomlin.com>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Tue, Apr 21, 2026 at 11:09:11AM -0400, Aaron Tomlin wrote:
> - 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:
Use double-colon syntax (i.e. ``For example::``) for literal code block
below.
> +
> + # cat /sys/kernel/debug/irq/irqs/87
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-04-30 7:08 UTC|newest]
Thread overview: 6+ 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
2026-04-30 7:08 ` Bagas Sanjaya [this message]
2026-05-16 14:12 ` Aaron Tomlin
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=afMAAL4lB72HiSQI@archie.me \
--to=bagasdotme@gmail.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.