[PATCH v2 0/2] Make iowait_boost optional and default to policy
iowait_boost is causing power regression on our arm64 SoC. Really going to max frequency is bad for power on mobile devices and not wise. These patches make it optional and default to what the policy suggests coming from the cpufreq driver as input to the governor. Here are some power numbers collected on an arm64 based Qualcomm SoC on a mobile device running a YouTube video for 30 seconds: Before: 8.042533 mWh After: 7.948377 mWh Energy savings is ~1.2% Joel Fernandes (2): cpufreq: Make iowait boost a policy option sched: Use iowait boost policy option in schedutil drivers/cpufreq/intel_pstate.c | 1 + include/linux/cpufreq.h | 3 +++ kernel/sched/cpufreq_schedutil.c | 32 3 files changed, 36 insertions(+) Cc: Srinivas PandruvadaCc: Len Brown Cc: Rafael J. Wysocki Cc: Viresh Kumar Cc: Ingo Molnar Cc: Peter Zijlstra -- 2.13.0.303.g4ebf302169-goog
[PATCH v2 0/2] Make iowait_boost optional and default to policy
iowait_boost is causing power regression on our arm64 SoC. Really going to max frequency is bad for power on mobile devices and not wise. These patches make it optional and default to what the policy suggests coming from the cpufreq driver as input to the governor. Here are some power numbers collected on an arm64 based Qualcomm SoC on a mobile device running a YouTube video for 30 seconds: Before: 8.042533 mWh After: 7.948377 mWh Energy savings is ~1.2% Joel Fernandes (2): cpufreq: Make iowait boost a policy option sched: Use iowait boost policy option in schedutil drivers/cpufreq/intel_pstate.c | 1 + include/linux/cpufreq.h | 3 +++ kernel/sched/cpufreq_schedutil.c | 32 3 files changed, 36 insertions(+) Cc: Srinivas Pandruvada Cc: Len Brown Cc: Rafael J. Wysocki Cc: Viresh Kumar Cc: Ingo Molnar Cc: Peter Zijlstra -- 2.13.0.303.g4ebf302169-goog