From: Michael Ellerman <mpe@ellerman.id.au>
To: Preeti U Murthy <preeti@linux.vnet.ibm.com>
Cc: rafael.j.wysocki@intel.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: cpuidle/powernv: Read target_residency value of idle states from DT if available
Date: Tue, 27 Jan 2015 17:28:10 +1100 [thread overview]
Message-ID: <1422340090.27133.4.camel@ellerman.id.au> (raw)
In-Reply-To: <54C70DDD.9040408@linux.vnet.ibm.com>
On Tue, 2015-01-27 at 09:32 +0530, Preeti U Murthy wrote:
> On 01/23/2015 10:29 AM, Michael Ellerman wrote:
> > On Tue, 2015-20-01 at 11:26:49 UTC, Preeti U Murthy wrote:
> >> @@ -177,34 +178,39 @@ static int powernv_add_idle_states(void)
> >
> >> for (i = 0; i < dt_idle_states; i++) {
> >>
> >> flags = be32_to_cpu(idle_state_flags[i]);
> >> -
> >> - /* Cpuidle accepts exit_latency in us and we estimate
> >> - * target residency to be 10x exit_latency
> >> + /*
> >> + * Cpuidle accepts exit_latency and target_residency in us.
> >> + * Use default target_residency values if f/w does not expose it.
> >> */
> >> - latency_ns = be32_to_cpu(idle_state_latency[i]);
> >> if (flags & OPAL_PM_NAP_ENABLED) {
> >> /* Add NAP state */
> >> strcpy(powernv_states[nr_idle_states].name, "Nap");
> >> strcpy(powernv_states[nr_idle_states].desc, "Nap");
> >> powernv_states[nr_idle_states].flags = 0;
> >> - powernv_states[nr_idle_states].exit_latency =
> >> - ((unsigned int)latency_ns) / 1000;
> >> - powernv_states[nr_idle_states].target_residency =
> >> - ((unsigned int)latency_ns / 100);
> >> + powernv_states[nr_idle_states].target_residency = 100;
> >> powernv_states[nr_idle_states].enter = &nap_loop;
> >> - nr_idle_states++;
> >
> > That looks wrong? Or do you mean to do that?
>
> If you are pointing at the lines that remove increment of
> nr_idle_states, it has to be done so towards the end of the iteration
> because we are yet to populate the exit_latency and target_residency
> outside of these conditions using this index.
Oh OK I think I get it, it's not clear at all.
The resulting code is:
for (i = 0; i < dt_idle_states; i++) {
flags = be32_to_cpu(idle_state_flags[i]);
/*
* Cpuidle accepts exit_latency and target_residency in us.
* Use default target_residency values if f/w does not expose it.
*/
if (flags & OPAL_PM_NAP_ENABLED) {
/* Add NAP state */
strcpy(powernv_states[nr_idle_states].name, "Nap");
strcpy(powernv_states[nr_idle_states].desc, "Nap");
powernv_states[nr_idle_states].flags = 0;
powernv_states[nr_idle_states].target_residency = 100;
powernv_states[nr_idle_states].enter = &nap_loop;
}
if (flags & OPAL_PM_SLEEP_ENABLED ||
flags & OPAL_PM_SLEEP_ENABLED_ER1) {
/* Add FASTSLEEP state */
strcpy(powernv_states[nr_idle_states].name, "FastSleep");
strcpy(powernv_states[nr_idle_states].desc, "FastSleep");
powernv_states[nr_idle_states].flags = CPUIDLE_FLAG_TIMER_STOP;
powernv_states[nr_idle_states].target_residency = 300000;
powernv_states[nr_idle_states].enter = &fastsleep_loop;
}
powernv_states[nr_idle_states].exit_latency =
((unsigned int)latency_ns[i]) / 1000;
if (!rc) {
powernv_states[nr_idle_states].target_residency =
((unsigned int)residency_ns[i]) / 1000;
}
nr_idle_states++;
}
Which looks like you could potentially overwrite the first set of values, "Nap"
with "FastSleep". But I think what you're going to tell me is that flags can
never satisfy both conditions, so we will only ever execute either the "Nap"
case OR the "FastSleep".
If so please change the code to make that obvious, ie. by using else if.
cheers
prev parent reply other threads:[~2015-01-27 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 11:32 [PATCH] cpuidle/powernv: Read target_residency value of idle states from DT if available Preeti U Murthy
2015-01-20 5:45 ` Michael Ellerman
2015-01-20 11:26 ` Preeti U Murthy
2015-01-20 11:52 ` PowerMac G5 Quad Issue reporting luigi burdo
2015-01-21 6:39 ` Michel Dänzer
2015-01-21 8:13 ` luigi burdo
2015-01-23 4:59 ` cpuidle/powernv: Read target_residency value of idle states from DT if available Michael Ellerman
2015-01-27 4:02 ` Preeti U Murthy
2015-01-27 6:28 ` Michael Ellerman [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=1422340090.27133.4.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=rafael.j.wysocki@intel.com \
/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).