linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Chris Friesen <chris.friesen@windriver.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: IRQs in /proc/irq/* that aren't listed in /proc/interrupts?
Date: Mon, 12 Oct 2020 21:37:38 +0200	[thread overview]
Message-ID: <87wnzvp75p.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <c74773ba-10ff-ba3a-b144-da5c2a34c74e@windriver.com>

Chris,

On Mon, Oct 12 2020 at 12:40, Chris Friesen wrote:
> On one of my X86-64 systems /proc/interrupts starts with the following 
> interrupts (per-cpu info snipped):
>
>    0:      IR-IO-APIC-edge      timer
>     4:      IR-IO-APIC-edge      serial
>     8:      IR-IO-APIC-edge      rtc0
>     9:      IR-IO-APIC-fasteoi   acpi
>    17:      IR-IO-APIC-fasteoi   ehci_hcd:usb1, hpilo
>
>
> On this same system /proc/irq shows these interrupts:
>
> 0-15, 17
>
> Is there any way to determine what the interrupts are that aren't listed 
> in /proc/interrupts?

They are simply unused.

> Six of them are affined to all CPUs, and I'm trying to affine as many
> interrupts as possible to housekeeping CPUs to free up application
> CPUs for low-latency operations.

Affining unused and therefore disabled interrupts is a pretty pointless
exercise.

Thanks,

        tglx

  reply	other threads:[~2020-10-12 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 18:40 IRQs in /proc/irq/* that aren't listed in /proc/interrupts? Chris Friesen
2020-10-12 19:37 ` Thomas Gleixner [this message]
2020-10-13  6:21   ` Chris Friesen

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=87wnzvp75p.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=chris.friesen@windriver.com \
    --cc=linux-kernel@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).