From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Suresh.Srinivasan@arm.com,
Amit Kucheria <amit.kucheria@linaro.org>,
Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
Subject: Re: [Query-CPUIdle]: Not much activity in C0 state
Date: Tue, 03 Sep 2013 15:32:56 +0200 [thread overview]
Message-ID: <5225E508.2060407@linaro.org> (raw)
In-Reply-To: <CAKohpo=OuYK7vhoG6a4REd-XuGMP63NTKhd8TWJmKo1R6rDp7g@mail.gmail.com>
On 08/27/2013 12:23 PM, Viresh Kumar wrote:
> Hi Guys,
>
> I was trying to run following on my thinkpad:
>
> watch -n1 cat /sys/devices/system/cpu/cpu*/cpuidle/state*/usage
>
> I can see lots of activities on State 1-4, but not much on state 0..
> I thought we should enter this state as soon as we come out to
> non-idle state.. And so this count must be changing quite rapidly.
>
> Is this a bug?
Hi Viresh,
the menu governor tries always to stick to C1 (state1) as default state,
look at the menu_select function. The state0 (not C0 but 'poll') will
happen when the next timer event is less than 5us, this occurs rarely.
You can easily spot it by doing while $(true); usleep 2; done
The poll state is x86 specific where the cpu detects the 'rep nop'
instructions to do some power saving.
Hope that helps
-- 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:[~2013-09-03 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 10:23 [Query-CPUIdle]: Not much activity in C0 state Viresh Kumar
2013-09-03 13:32 ` 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=5225E508.2060407@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Sudeep.KarkadaNagesha@arm.com \
--cc=Suresh.Srinivasan@arm.com \
--cc=amit.kucheria@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.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 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).