From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Len Brown <len.brown@intel.com>,
Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: Disabling power management firmware decisions
Date: Thu, 19 Mar 2015 16:34:52 +0100 [thread overview]
Message-ID: <550AEC9C.5030308@linaro.org> (raw)
In-Reply-To: <4773622.DqM2RS9PPh@vostro.rjw.lan>
On 03/19/2015 03:08 PM, Rafael J. Wysocki wrote:
> On Thursday, March 19, 2015 02:33:34 PM Daniel Lezcano wrote:
>>
>> Hi,
>>
>> I would like to do some experiments with the x86 platform but I am
>> facing one big issue.
>>
>> When I use the rapl register to measure the energy consumption with
>> turbostat and another tool written by me. I see no differences between
>> my kernel changes while using the idlestat tool, I see big differences
>> in the idle state durations with the traces.
>>
>> I remember on x86 the firmware overrides all kernel decisions to do the
>> power management. So I assume, it is possible my changes are not
>> measurable because of that.
>>
>> Is there a way to tell the firmware to stop overriding the kernel
>> decisions in order to let the kernel handle idle/dvfs on its own ?
>
> The short answer to that is no, there isn't. It also may not be firmware,
> but hardware.
mmrfh, that's not funny :(
Thanks for the answer.
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2015-03-19 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 13:33 Disabling power management firmware decisions Daniel Lezcano
2015-03-19 14:08 ` Rafael J. Wysocki
2015-03-19 15:34 ` Daniel Lezcano [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=550AEC9C.5030308@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).