@@ -1030,7 +1030,8 @@ void init_entity_runnable_average(struct sched_entity *se)
10301030 * With new tasks being created, their initial util_avgs are extrapolated
10311031 * based on the cfs_rq's current util_avg:
10321032 *
1033- * util_avg = cfs_rq->util_avg / (cfs_rq->load_avg + 1) * se.load.weight
1033+ * util_avg = cfs_rq->avg.util_avg / (cfs_rq->avg.load_avg + 1)
1034+ * * se_weight(se)
10341035 *
10351036 * However, in many cases, the above util_avg does not give a desired
10361037 * value. Moreover, the sum of the util_avgs may be divergent, such
@@ -1077,7 +1078,7 @@ void post_init_entity_util_avg(struct task_struct *p)
10771078
10781079 if (cap > 0 ) {
10791080 if (cfs_rq -> avg .util_avg != 0 ) {
1080- sa -> util_avg = cfs_rq -> avg .util_avg * se -> load . weight ;
1081+ sa -> util_avg = cfs_rq -> avg .util_avg * se_weight ( se ) ;
10811082 sa -> util_avg /= (cfs_rq -> avg .load_avg + 1 );
10821083
10831084 if (sa -> util_avg > cap )
@@ -7898,8 +7899,8 @@ eenv_pd_max_util(struct energy_env *eenv, struct cpumask *pd_cpus,
78987899 * Performance domain frequency: utilization clamping
78997900 * must be considered since it affects the selection
79007901 * of the performance domain frequency.
7901- * NOTE: in case RT tasks are running, by default the
7902- * FREQUENCY_UTIL's utilization can be max OPP.
7902+ * NOTE: in case RT tasks are running, by default the min
7903+ * utilization can be max OPP.
79037904 */
79047905 eff_util = effective_cpu_util (cpu , util , & min , & max );
79057906
0 commit comments