From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: viresh.kumar@linaro.org, rjw@rjwysocki.net
Cc: linux-pm@vger.kernel.org, dirk.j.brandewie@intel.com,
shreyas@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
patrick.marlier@gmail.com, linuxppc-dev@ozlabs.org,
dirk.brandewie@gmail.com
Subject: [PATCH V2 0/2] cpufreq/powernv: Set core pstate to a minimum just before hotplugging it out
Date: Fri, 05 Sep 2014 13:09:32 +0530 [thread overview]
Message-ID: <20140905073812.3629.29175.stgit@preeti.in.ibm.com> (raw)
Today cpus go to winkle when they are offlined. Since it is the deepest
idle state that we have, it is expected to save good amount of power as compared
to online state, where cores can enter nap/fastsleep only which are
shallower idle states.
However we observed no powersavings with winkle as compared to nap/fastsleep
and traced the problem to the pstate of the core being kept at a high even
when the core is offline. This can keep the socket pstate high, thus burning
power unnecessarily. This patchset fixes this issue.
Changes in V2: Changed smp_call_function_any() to smp_call_function_single() in Patch[2/2]
---
Preeti U Murthy (2):
cpufreq: Allow stop CPU callback to be used by all cpufreq drivers
powernv/cpufreq: Set the pstate of the last hotplugged out cpu in policy->cpus to minimum
drivers/cpufreq/cpufreq.c | 2 +-
drivers/cpufreq/powernv-cpufreq.c | 9 +++++++++
2 files changed, 10 insertions(+), 1 deletion(-)
--
next reply other threads:[~2014-09-05 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 7:39 Preeti U Murthy [this message]
2014-09-05 7:40 ` [PATCH V2 1/2] cpufreq: Allow stop CPU callback to be used by all cpufreq drivers Preeti U Murthy
2014-09-05 7:40 ` [PATCH V2 2/2] powernv/cpufreq: Set the pstate of the last hotplugged out cpu in policy->cpus to minimum Preeti U Murthy
2014-09-05 7:41 ` [PATCH V2 0/2] cpufreq/powernv: Set core pstate to a minimum just before hotplugging it out Viresh Kumar
2014-09-09 0:16 ` Rafael J. Wysocki
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=20140905073812.3629.29175.stgit@preeti.in.ibm.com \
--to=preeti@linux.vnet.ibm.com \
--cc=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=patrick.marlier@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=shreyas@linux.vnet.ibm.com \
--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).