linux-kernel - Re: [PATCH x86] [2/16] Add a counter for per cpu clocksource watchdog checks and report them 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: <20080104085327.GB28740@elte.hu>
Date:	Fri, 4 Jan 2008 09:53:28 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <ak@...e.de>
Cc:	tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH x86] [2/16] Add a counter for per cpu clocksource
	watchdog checks and report them in /proc/interrupts

* Andi Kleen <ak@...e.de> wrote:

> While infrequent it's better if all per CPU events have a counter.
> 
> Only done for x86 currently.

while i agree with exposing this counter, /proc/interrupts is the wrong 
place for this - please add it to /proc/timer_list instead, that's where 
we put all the time related debug info - it already has per cpu printout 
sections. And that way it's much simpler as well. (no need to modify all 
the architectures)

	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/