On 28-10-17, 02:59, Joel Fernandes wrote:
> Since the recent remote cpufreq callback work, its possible that a cpufreq
> update is triggered from a remote CPU. For single policies however, the
> current
> code uses the local CPU when trying to determine if the remote sg_cpu entered
> idle or is busy. This is incorrect. To remedy this, compare with the nohz tick
> idle_calls counter of the remote CPU.
>
> Cc: Rafael J. Wysocki <[email protected]>
> Cc: Viresh Kumar <[email protected]>
> Cc: Ingo Molnar <[email protected]>
> Cc: Peter Zijlstra <[email protected]>
> Cc: Frederic Weisbecker <[email protected]>
> Cc: Thomas Gleixner <[email protected]>
Fixes: 674e75411fc2 ("sched: cpufreq: Allow remote cpufreq callbacks")
> Signed-off-by: Joel Fernandes <[email protected]>
> ---
> include/linux/tick.h | 1 +
> kernel/sched/cpufreq_schedutil.c | 2 +-
> kernel/time/tick-sched.c | 13 +++++++++++++
> 3 files changed, 15 insertions(+), 1 deletion(-)
Acked-by: Viresh Kumar <[email protected]>
--
viresh
