linux-kernel - Re: IRQs in /proc/irq/* that aren't listed in /proc/interrupts?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87wnzvp75p.fsf@nanos.tec.linutronix.de>
Date:   Mon, 12 Oct 2020 21:37:38 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Chris Friesen <chris.friesen@...driver.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: IRQs in /proc/irq/* that aren't listed in /proc/interrupts?

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