From: Chris Friesen <chris.friesen@windriver.com>
To: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: IRQs in /proc/irq/* that aren't listed in /proc/interrupts?
Date: Tue, 13 Oct 2020 00:21:02 -0600 [thread overview]
Message-ID: <0d3cff4f-619f-3479-2195-e07451636249@windriver.com> (raw)
In-Reply-To: <87wnzvp75p.fsf@nanos.tec.linutronix.de>
On 10/12/2020 1:37 PM, Thomas Gleixner wrote:
> 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
I wonder if it might be clearer to just not report them at all if
they're not used?
Anyways, thanks for the explanation.
Chris
prev parent reply other threads:[~2020-10-13 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 18:40 Chris Friesen
2020-10-12 19:37 ` Thomas Gleixner
2020-10-13 6:21 ` Chris Friesen [this message]
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=0d3cff4f-619f-3479-2195-e07451636249@windriver.com \
--to=chris.friesen@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®