linux-kernel - Re: 2.6.20-rc6-mm3

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]

Date:	Wed, 07 Feb 2007 00:36:29 +0100
From:	Thomas Gleixner <tglx@...utronix.de>
To:	dwalker@...sta.com
Cc:	Ingo Molnar <mingo@...e.hu>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-rc6-mm3

On Tue, 2007-02-06 at 15:22 -0800, Daniel  Walker wrote:
> > > What about the statistics for the other interrupts in the system ? It 
> > > clearly doesn't list all interrupts in the system .
> > 
> > what is your point?
> 
> Isn't the listing inconsistent ? /proc/interrupts only showing some
> special interrupts, and not others .. 

It shows _ALL_ used interrupts in the system. There is no point to let
it show NR_IRQ interrupts with a event count = 0.

> For example it shows NMI which is
> not related to request_irq() .. It shows some clock driver devices
> (timer, NMI, LOC) and not others (clock event devices) ..

PIT is a clock event device and uses IRQ0, where the interrupt count is
displayed:

0:    3022812          0   IO-APIC-edge      timer

Local APIC timer is a clock event device too and the interrupt count is
displayed as well:

LOC:     177795    1755941 

There are no other clock event devices in a PC system at the moment
and /proc/interrupt does not care, whether the interrupt was setup for a
clock event device or something else. It displays the name which is
given in the irqaction struct and does not care what it means. I did not
change the name in the IRQ#0 setup, so it still displays "timer" (which
can either be PIT or HPET), but this is something the interrupt layer
does not know and does not care about.

The special interrupts, which are not handled by the generic IRQ layer
(LOC, NMI) are displayed to have the complete statistics available.

We did not change anything on that. The changed behavior you are
observing (IRQ#0 is not incrementing) is reflecting the reality of the
system. IRQ#0 is not firing, so it does not increment.

	tglx

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/