From: Ingo Molnar <mingo@elte.hu>
To: Paul Mundt <lethal@linux-sh.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: register_timer_hook use in arch/sh/oprofile
Date: Wed, 24 Jun 2009 14:45:42 +0200 [thread overview]
Message-ID: <20090624124542.GB32306@elte.hu> (raw)
In-Reply-To: <20090624123416.GB9510@linux-sh.org>
* Paul Mundt <lethal@linux-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
next prev parent reply other threads:[~2009-06-24 12:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 11:11 Martin Schwidefsky
2009-06-24 11:29 ` Paul Mundt
2009-06-24 12:17 ` Ingo Molnar
2009-06-24 12:25 ` Paul Mundt
2009-06-24 12:37 ` Ingo Molnar
2009-06-24 12:40 ` Paul Mackerras
2009-06-24 12:47 ` Ingo Molnar
2009-06-24 12:28 ` Martin Schwidefsky
2009-06-24 12:34 ` Paul Mundt
2009-06-24 12:45 ` Ingo Molnar [this message]
2009-06-24 13:14 ` Paul Mundt
2009-06-24 13:24 ` Ingo Molnar
2009-06-26 7:01 ` Peter Zijlstra
2009-06-26 7:23 ` Ingo Molnar
2009-06-26 7:26 ` Paul Mundt
2009-06-26 7:36 ` Peter Zijlstra
2009-06-24 12:54 ` Martin Schwidefsky
2009-12-16 4:52 ` Paul Mundt
2009-12-16 7:21 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090624124542.GB32306@elte.hu \
--to=mingo@elte.hu \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome