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] [day] [month] [year] [list]
Message-ID: <0d3cff4f-619f-3479-2195-e07451636249@windriver.com>
Date:   Tue, 13 Oct 2020 00:21:02 -0600
From:   Chris Friesen <chris.friesen@...driver.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: IRQs in /proc/irq/* that aren't listed in /proc/interrupts?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ