sched: fair: Always use energy aware wakeups
Currently, EAS scheduling ignores energy considerations for fork-wakeups
or if the cpu we're doing the wakeup on is overutilized. Unfortunately,
this also breaks the other considerations for placement such as C-state,
colocation etc. Let's always run the energy_aware_wake_cpu function and
introduce optimizations in that function instead.
Change-Id: I14c85beaa162b9013a9a648d6a64b9fc02f02915
Signed-off-by:
Vikram Mulukutla <markivx@codeaurora.org>
Loading
Please register or sign in to comment