linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <schwenderjonathan@gmail.com>
To: <linux-rt-users@vger.kernel.org>
Subject: What are managed IRQs?
Date: Thu, 21 Jan 2021 16:47:45 +0100	[thread overview]
Message-ID: <013a01d6f00c$c345be90$49d13bb0$@gmail.com> (raw)

Hi everyone,

isolcpus has the option `managed_irq`, which supposedly assigns the IRQs to
housekeeping CPUs if possible. According to the description of isolcpus, the
affinity of managed IRQs can not be changed via /proc/irq.
I've searched the kernel documentation and the kernel source code for 
more information about managed IRQs / managed interrupts, but haven't found 
any documentation (aside from isolcpus).

Specifically, I'm interested in what makes managed IRQs different (as in 
why can't the affinity be changed via procfs), and
what kind of IRQs are "managed"? 

Also, I'd like to verify if the cmdline parameter `irqaffinity` 
affects managed IRQs, or if it only modifies the default affinity for IRQs
which can be changed via procfs.

Thanks

Jonathan


             reply	other threads:[~2021-01-21 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 15:47 schwenderjonathan [this message]
2021-01-22 13:03 ` What are managed IRQs? Sebastian Andrzej Siewior

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='013a01d6f00c$c345be90$49d13bb0$@gmail.com' \
    --to=schwenderjonathan@gmail.com \
    --cc=linux-rt-users@vger.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;
as well as URLs for NNTP newsgroup(s).