From: Christian Loehle <christian.loehle@arm.com>
To: linux-kernel@vger.kernel.org
Cc: vincent.guittot@linaro.org, mingo@redhat.com,
peterz@infradead.org, dietmar.eggemann@arm.com,
Christian Loehle <christian.loehle@arm.com>
Subject: [PATCH] sched/fair: Remove stale FREQUENCY_UTIL comment
Date: Tue, 5 Mar 2024 09:51:11 +0000 [thread overview]
Message-ID: <20240305095111.777525-1-christian.loehle@arm.com> (raw)
effective_cpu_util() flags were removed, so remove the comment part
mentioning it.
commit 9c0b4bb7f6303 ("sched/cpufreq: Rework schedutil governor performance estimation")
reworked effective_cpu_util() removing enum cpu_util_type.
Signed-off-by: Christian Loehle <christian.loehle@arm.com>
---
kernel/sched/fair.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 533547e3c90a..6b0c47d00fd3 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -7849,8 +7849,6 @@ eenv_pd_max_util(struct energy_env *eenv, struct cpumask *pd_cpus,
* Performance domain frequency: utilization clamping
* must be considered since it affects the selection
* of the performance domain frequency.
- * NOTE: in case RT tasks are running, by default the
- * FREQUENCY_UTIL's utilization can be max OPP.
*/
eff_util = effective_cpu_util(cpu, util, &min, &max);
--
2.34.1
next reply other threads:[~2024-03-05 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 9:51 Christian Loehle [this message]
2024-03-05 15:05 ` Vincent Guittot
2024-03-05 15:18 ` Christian Loehle
2024-03-05 15:39 ` Vincent Guittot
2024-05-17 8:06 ` [tip: sched/urgent] " tip-bot2 for Christian Loehle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240305095111.777525-1-christian.loehle@arm.com \
--to=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®