From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: mitake@dcl.info.waseda.ac.jp
Cc: mingo@elte.hu, fweisbec@gmail.com, linux@brodo.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Adding transition of CPU frequency counting support to perfcounters
Date: Sat, 18 Jul 2009 18:09:15 +0200 [thread overview]
Message-ID: <1247933355.6597.11.camel@laptop> (raw)
In-Reply-To: <20090718.231137.187581409.mitake@dcl.info.waseda.ac.jp>
On Sat, 2009-07-18 at 23:11 +0900, mitake@dcl.info.waseda.ac.jp wrote:
>
> Oh, my perf could count cpufreq events!
> Thanks for your nice advice!
>
> % perf stat -a sleep 60
>
> Performance counter stats for 'sleep 60':
>
> 479088.075595 task-clock-msecs # 7.984 CPUs
> 199080 context-switches # 0.000 M/sec
> 19584 CPU-migrations # 0.000 M/sec
> 322978 page-faults # 0.001 M/sec
> 29 cpufreq-up # 0.000 M/sec
> 42 cpufreq-down # 0.000 M/sec
> 73703367828 cycles # 153.841 M/sec
> 52005203450 instructions # 0.706 IPC
> 209762467 cache-references # 0.438 M/sec
> 84916856 cache-misses # 0.177 M/sec
>
> 60.009508200 seconds time elapsed
>
> And I'm using ondemand governor now,
> so kernel thread [kondemand] context causes freq transition.
> I didn't notice that...
>
> Could you merge this patch?
> Can I send this patch with descriptions and Signed-off-by?
Why, what is the usecase?
next prev parent reply other threads:[~2009-07-18 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 2:08 [PATCH][RFC] Adding transition of CPU frequency counting support to perfcounters Hitoshi Mitake
2009-07-18 9:31 ` Ingo Molnar
2009-07-18 14:11 ` mitake
2009-07-18 16:09 ` Peter Zijlstra [this message]
2009-07-21 1:46 ` Hitoshi Mitake
2009-08-02 20:13 ` 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=1247933355.6597.11.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=mingo@elte.hu \
--cc=mitake@dcl.info.waseda.ac.jp \
/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