diff options
author | Joel Fernandes <[email protected]> | 2017-12-15 07:39:43 -0800 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2018-01-10 11:30:30 +0100 |
commit | 9783be2c0e90bbaceec3c471c4fb017bff7293ba (patch) | |
tree | a2fd04c38ae2e59ebd7f99ba2bac92efa21791d8 | |
parent | 18cec7e0ddd5e28b7722f7049d715873373be3e9 (diff) |
sched/fair: Correct obsolete comment about cpufreq_update_util()
Since the remote cpufreq callback work, the cpufreq_update_util() call can happen
from remote CPUs. The comment about local CPUs is thus obsolete. Update it
accordingly.
Signed-off-by: Joel Fernandes <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Reviewed-by: Viresh Kumar <[email protected]>
Cc: Android Kernel <[email protected]>
Cc: Atish Patra <[email protected]>
Cc: Chris Redpath <[email protected]>
Cc: Dietmar Eggemann <[email protected]>
Cc: EAS Dev <[email protected]>
Cc: Frederic Weisbecker <[email protected]>
Cc: Josef Bacik <[email protected]>
Cc: Juri Lelli <[email protected]>
Cc: Len Brown <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Morten Ramussen <[email protected]>
Cc: Patrick Bellasi <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Rafael J. Wysocki <[email protected]>
Cc: Rohit Jain <[email protected]>
Cc: Saravana Kannan <[email protected]>
Cc: Srinivas Pandruvada <[email protected]>
Cc: Steve Muckle <[email protected]>
Cc: Steven Rostedt <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: Vikram Mulukutla <[email protected]>
Cc: Vincent Guittot <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
-rw-r--r-- | kernel/sched/fair.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 3e7606d3ad0f..59e66a5848d0 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -3020,9 +3020,7 @@ static inline void cfs_rq_util_change(struct cfs_rq *cfs_rq) /* * There are a few boundary cases this might miss but it should * get called often enough that that should (hopefully) not be - * a real problem -- added to that it only calls on the local - * CPU, so if we enqueue remotely we'll miss an update, but - * the next tick/schedule should update. + * a real problem. * * It will not get called when we go idle, because the idle * thread is a different class (!fair), nor will the utilization |