Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit a744490f authored by Juri Lelli's avatar Juri Lelli Committed by Rafael J. Wysocki
Browse files

cpufreq: schedutil: remove stale comment 



After commit 794a56eb (sched/cpufreq: Change the worker kthread to
SCHED_DEADLINE) schedutil kthreads are "ignored" for a clock frequency
selection point of view, so the potential corner case for RT tasks is not
possible at all now.

Remove the stale comment mentioning it.

Signed-off-by: default avatarJuri Lelli <juri.lelli@redhat.com>
Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
parent 75bc37fe

kernel/sched/cpufreq_schedutil.c

+0 −13
Original line number Original line Diff line number Diff line
@@ -396,19 +396,6 @@ static void sugov_irq_work(struct irq_work *irq_work) 




	sg_policy = container_of(irq_work, struct sugov_policy, irq_work);

	sg_policy = container_of(irq_work, struct sugov_policy, irq_work);





	/*

	 * For RT tasks, the schedutil governor shoots the frequency to maximum.

	 * Special care must be taken to ensure that this kthread doesn't result

	 * in the same behavior.

	 *

	 * This is (mostly) guaranteed by the work_in_progress flag. The flag is

	 * updated only at the end of the sugov_work() function and before that

	 * the schedutil governor rejects all other frequency scaling requests.

	 *

	 * There is a very rare case though, where the RT thread yields right

	 * after the work_in_progress flag is cleared. The effects of that are

	 * neglected for now.

	 */

	kthread_queue_work(&sg_policy->worker, &sg_policy->work);

	kthread_queue_work(&sg_policy->worker, &sg_policy->work);

}

}