diff options
| author | Hao Jia <[email protected]> | 2023-06-13 08:20:11 +0000 |
|---|---|---|
| committer | Peter Zijlstra <[email protected]> | 2023-06-16 20:08:13 +0000 |
| commit | ebb83d84e49b54369b0db67136a5fe1087124dcc (patch) | |
| tree | b0db940a0de97b2759308c5bbb715a08f0d6513e /drivers/clocksource/hyperv_timer.c | |
| parent | sched/core: Avoid double calling update_rq_clock() in __balance_push_cpu_stop() (diff) | |
| download | kernel-ebb83d84e49b54369b0db67136a5fe1087124dcc.tar.gz kernel-ebb83d84e49b54369b0db67136a5fe1087124dcc.zip | |
sched/core: Avoid multiple calling update_rq_clock() in __cfsb_csd_unthrottle()
After commit 8ad075c2eb1f ("sched: Async unthrottling for cfs
bandwidth"), we may update the rq clock multiple times in the loop of
__cfsb_csd_unthrottle().
A prior (although less common) instance of this problem exists in
unthrottle_offline_cfs_rqs().
Cure both by ensuring update_rq_clock() is called before the loop and
setting RQCF_ACT_SKIP during the loop, to supress further updates.
The alternative would be pulling update_rq_clock() out of
unthrottle_cfs_rq(), but that gives an even bigger mess.
Fixes: 8ad075c2eb1f ("sched: Async unthrottling for cfs bandwidth")
Reviewed-By: Ben Segall <[email protected]>
Suggested-by: Vincent Guittot <[email protected]>
Signed-off-by: Hao Jia <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Reviewed-by: Vincent Guittot <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'drivers/clocksource/hyperv_timer.c')
0 files changed, 0 insertions, 0 deletions
