linux-kernel - Re: register_timer_hook use in arch/sh/oprofile

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, 24 Jun 2009 14:45:42 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Paul Mundt <lethal@...ux-sh.org>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: register_timer_hook use in arch/sh/oprofile

* Paul Mundt <lethal@...ux-sh.org> wrote:

> My current plan is to migrate things over to the perf_counter API 
> and annoy Ingo with my interrupt deprived counters ;-)

Please do :-)

I just wrote a longer explanation about them: i think they can be 
made full-blown hardware counters, which in the end would be 
basically just as capable as 'real' IRQ capable counters.

The main complication that such counters bring is that in their 'own 
metric' they do interrupt periods in an 'irregular' way (because 
they interrupt in the nanosec metric - being hrtimers) - but both 
the tools can deal with uneven periods just fine and the auto-freq 
code can auto-balance based on this just fine too.

So you should be able to implement this within arch/sh/ with 
existing perf_counter facilities and hrtimers, or you can help us 
librarize it in kernel/perf_counter.c some more, to minimize 
architecture code.

[ Of course, given that you are the first architecture to do this,
  you would be fair to expect some unexpected details along the way 
  as well ;-) ]

	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/