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: Wed, 12 Jun 2013 14:21:30 -0700 [thread overview]
Message-ID: <51B8E65A.7090102@hp.com> (raw)
In-Reply-To: <51B65589.5030700@hp.com>
On 06/10/2013 03:39 PM, Rick Jones wrote:
> On 06/10/2013 03:33 PM, David Ahern wrote:
>> On 6/10/13 4:28 PM, Rick Jones wrote:
>>>> 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?
>>
>> Yes, that should turn the server into a power-sucking space heater and
>> keep the cycles counter firing.
>
> Excellent - I can live with the server being a power-sucking space
> heater for the duration of my profiling. Heck, many of the servers I
> used to work on were always power-sucking space heaters :)
Just for the archives and anyone looking to go "space heater" in the
future - it is a Good Idea (tm) to disable hyper threads (at least with
this sort of hyper threading in E5-2670 processors) or you can have what
I presume are two HT's battling one another in the idle loop.
rick jones
prev parent reply other threads:[~2013-06-12 21:21 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
2013-06-10 22:33 ` David Ahern
2013-06-10 22:39 ` Rick Jones
2013-06-12 21:21 ` Rick Jones [this message]
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=51B8E65A.7090102@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.