Commit 73f29d2e authored May 04, 2017 by Vikram Mulukutla Committed by Rohit Gupta Dec 28, 2017

cpufreq: schedutil: Ignore work_in_progress



Blindly ignoring frequency updates because of work_in_progress can leave
the CPUs at the wrong frequency for a long time. It's better to update the
frequency immediately than wait for a future event that might take a long
time to come. The irq_work code already ignores double queuing of work. So,
that part of the code is still safe when the work_in_progress flag is
ignored.

Change-Id: Id0b3711314dfbfa18b5f4bce30a239ee3cf962d6
Signed-off-by: Vikram Mulukutla <markivx@codeaurora.org>
Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
Signed-off-by: Rohit Gupta <rohgup@codeaurora.org>

parent b9131989

kernel/sched/cpufreq_schedutil.c

+0 −3

Original line number	Diff line number	Diff line
		@@ -98,9 +98,6 @@ static bool sugov_should_update_freq(struct sugov_policy *sg_policy, u64 time)
		!cpufreq_can_do_remote_dvfs(sg_policy->policy))
		return false;

		if (sg_policy->work_in_progress)
		return false;

		if (unlikely(sg_policy->need_freq_update)) {
		sg_policy->need_freq_update = false;
		/*