From: Rick Jones <rick.jones2@hp.com>
To: David Ahern <dsahern@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: measuring and/or dealing with "idleness" and variable frequency
Date: Mon, 10 Jun 2013 15:28:09 -0700 [thread overview]
Message-ID: <51B652F9.4020402@hp.com> (raw)
In-Reply-To: <51B63847.1010008@hp.com>
On 06/10/2013 01:34 PM, Rick Jones wrote:
> On 06/08/2013 08:21 PM, David Ahern wrote:
>> On 6/6/13 11:46 AM, Rick Jones wrote:
>>> I am coming to "perf" (record -e cycles and report) from an old-time
>>> background where one could see the "idle routine" in a profile and know
>>> how "idle" (in terms of classic reporting a la top) a CPU was. Back
>>> then the frequency was fixed, the idle loop was always "running" when
>>> the CPU was idle and there were no hardware threads. Life was simple
>>> and good.
>>
>> You could use the scheduling events or context-switches to know when a
>> CPU is idle. Idle time for a CPU is one of the stats my perf-timehist
>> command shows. I just dumped it to LKML:
>> https://lkml.org/lkml/2013/6/7/656
>>
>> It's an RFC from an inclusion upstream but it has been used for over 2
>> years.
>
> I think I could get what I want from that - assuming I could get that to
> a kernel I can use in my test env, but am guessing it is rather more
> than I"m looking for at the moment. I'm wondering if there might be a
> simpler way to go - just get the idle loop to keep looping rather than
> halt (?) the thread, so there would still be cycle events in the PMU?
> (And perhaps set the system to a static, high-performance mode to avoid
> frequency changes and maybe even disable HT?)
Or, after having found
https://www.kernel.org/doc/Documentation/kernel-parameters.txt, perhaps
idle=poll?
rick jones
next prev parent reply other threads:[~2013-06-10 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 17:46 measuring and/or dealing with "idleness" and variable frequency Rick Jones
2013-06-09 3:21 ` David Ahern
2013-06-10 20:34 ` Rick Jones
2013-06-10 22:28 ` Rick Jones [this message]
2013-06-10 22:33 ` David Ahern
2013-06-10 22:39 ` Rick Jones
2013-06-12 21:21 ` Rick Jones
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=51B652F9.4020402@hp.com \
--to=rick.jones2@hp.com \
--cc=dsahern@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.