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: <aAijgnvHRYu_Dlqe@wunner.de>
Date: Wed, 23 Apr 2025 10:23:30 +0200
From: Lukas Wunner <lukas@...ner.de>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Jiri Slaby <jirislaby@...nel.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: IRQ domain logging?

On Tue, Apr 22, 2025 at 04:07:05PM -0500, Bjorn Helgaas wrote:
> This from an arm64 system is even more obscure to me:
> 
>   NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
>   GICv3: 256 SPIs implemented
>   Root IRQ handler: gic_handle_irq
>   GICv3: GICv3 features: 16 PPIs
>   kvm [1]: vgic interrupt IRQ18
>   xhci-hcd xhci-hcd.0.auto: irq 67, io mem 0xfe800000
> 
> I have no clue where irq 67 goes.

There's quite a bit of information available in /proc/interrupts,
/proc/irq/ and /sys/kernel/irq/, I guess that's what most people use.

Thanks,

Lukas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ