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

Commit 75920196 authored by Chen Yu's avatar Chen Yu Committed by Rafael J. Wysocki
Browse files

cpufreq: governors: Fix long idle detection logic in load calculation 



According to current code implementation, detecting the long
idle period is done by checking if the interval between two
adjacent utilization update handlers is long enough. Although
this mechanism can detect if the idle period is long enough
(no utilization hooks invoked during idle period), it might
not cover a corner case: if the task has occupied the CPU
for too long which causes no context switches during that
period, then no utilization handler will be launched until this
high prio task is scheduled out. As a result, the idle_periods
field might be calculated incorrectly because it regards the
100% load as 0% and makes the conservative governor who uses
this field confusing.

Change the detection to compare the idle_time with sampling_rate
directly.

Reported-by: default avatarArtem S. Tashkinov <t.artem@mailcity.com>
Signed-off-by: default avatarChen Yu <yu.c.chen@intel.com>
Acked-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
Cc: All applicable <stable@vger.kernel.org>
Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
parent 41ab43c9

drivers/cpufreq/cpufreq_governor.c

+5 −7
Original line number Diff line number Diff line
@@ -165,7 +165,7 @@ unsigned int dbs_update(struct cpufreq_policy *policy) 
			 * calls, so the previous load value can be used then.

			 */

			load = j_cdbs->prev_load;

		} else if (unlikely(time_elapsed > 2 * sampling_rate &&

		} else if (unlikely((int)idle_time > 2 * sampling_rate &&

				    j_cdbs->prev_load)) {

			/*

			 * If the CPU had gone completely idle and a task has
@@ -185,10 +185,8 @@ unsigned int dbs_update(struct cpufreq_policy *policy) 
			 * clear prev_load to guarantee that the load will be

			 * computed again next time.

			 *

			 * Detecting this situation is easy: the governor's

			 * utilization update handler would not have run during

			 * CPU-idle periods.  Hence, an unusually large

			 * 'time_elapsed' (as compared to the sampling rate)

			 * Detecting this situation is easy: an unusually large

			 * 'idle_time' (as compared to the sampling rate)

			 * indicates this scenario.

			 */

			load = j_cdbs->prev_load;
@@ -217,8 +215,8 @@ unsigned int dbs_update(struct cpufreq_policy *policy) 
			j_cdbs->prev_load = load;

		}



		if (time_elapsed > 2 * sampling_rate) {

			unsigned int periods = time_elapsed / sampling_rate;

		if (unlikely((int)idle_time > 2 * sampling_rate)) {

			unsigned int periods = idle_time / sampling_rate;



			if (periods < idle_periods)

				idle_periods = periods;