summaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorJoonwoo Park <joonwoop@codeaurora.org>2016-03-28 18:27:47 -0700
committerJeevan Shriram <jshriram@codeaurora.org>2016-04-22 15:05:24 -0700
commit2e0ebb0155f275b24a5feedfc8f28c5225fb8db6 (patch)
tree6fb03d69b4d247336db34db14a8aa28b5379cde2 /init
parentd4ca4d767f4c8a64ab212ddf2a9356c316de4f80 (diff)
sched: add option whether CPU C-state is used to guide task placement
There are CPUs that don't have an obvious low power mode exit latency penalty. Add a new Kconfig CONFIG_SCHED_HMP_CSTATE_AWARE which controls whether CPU C-state is used to guide task placement. CRs-fixed: 1006303 Change-Id: Ie8dbab8e173c3a1842d922f4d1fbd8cc4221789c Signed-off-by: Joonwoo Park <joonwoop@codeaurora.org>
Diffstat (limited to 'init')
-rw-r--r--init/Kconfig8
1 files changed, 8 insertions, 0 deletions
diff --git a/init/Kconfig b/init/Kconfig
index ad08a40a304b..9ad1ae9d9da8 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1162,6 +1162,14 @@ config SCHED_HMP
in their instructions per-cycle capability or the maximum
frequency they can attain.
+config SCHED_HMP_CSTATE_AWARE
+ bool "CPU C-state aware scheduler"
+ depends on SCHED_HMP
+ help
+ This feature will let the HMP scheduler optimize task placement
+ with CPUs C-state. If this is enabled, scheduler places tasks
+ onto the shallowest C-state CPU among the most power efficient CPUs.
+
config CHECKPOINT_RESTORE
bool "Checkpoint/restore support" if EXPERT
select PROC_CHILDREN