[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140905073812.3629.29175.stgit@preeti.in.ibm.com>
Date: Fri, 05 Sep 2014 13:09:32 +0530
From: Preeti U Murthy <preeti@...ux.vnet.ibm.com>
To: viresh.kumar@...aro.org, rjw@...ysocki.net
Cc: linux-pm@...r.kernel.org, dirk.j.brandewie@...el.com,
shreyas@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
patrick.marlier@...il.com, linuxppc-dev@...abs.org,
dirk.brandewie@...il.com, svaidy@...ux.vnet.ibm.com
Subject: [PATCH V2 0/2] cpufreq/powernv: Set core pstate to a minimum just
before hotplugging it out
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(-)
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists