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]

Message-ID: <20070206231421.GA18654@elte.hu>
Date:	Wed, 7 Feb 2007 00:14:21 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-rc6-mm3


* Daniel Walker <dwalker@...sta.com> wrote:

> On Tue, 2007-02-06 at 23:56 +0100, Ingo Molnar wrote:
> 
> > changing the current 'timer' entry (which is line 2 of /proc/interrupts) 
> > to be 'listed as lapic-timer' and to 'replace it with the count from 
> > LOC' is faking a count in a line where nothing like that should be.
> 
> This point is getting irrelevant ..

it is very much relevant: faking a count is something we /dont/ want to 
do with /proc/interrupts, for (very) basic compatibility, simplicity and 
policy reasons. And that is precisely what your suggestion was to 
'solve' this supposed 'problem' - so it's very much relevant.

> > the kernel simply displays reality: IRQ#0 isnt increasing because 
> > it's not used, and LOC (local apic timers) is increasing.
> 
> 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?

	Ingo
-
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/