summaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-04-05 19:07:57 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2018-04-07 18:48:24 +0200
commit23a8d888107ce4ce444eab2dcebf4cfb3578770b (patch)
tree2147dbac5c1e70ada0deb4d9e9197a6ccdbb299e /firmware
parent45f1ff59e27ca59d33cc1a317e669d90022ccf7d (diff)
downloadlinux-23a8d888107ce4ce444eab2dcebf4cfb3578770b.tar.bz2
time: tick-sched: Split tick_nohz_stop_sched_tick()
In order to address the issue with short idle duration predictions by the idle governor after the scheduler tick has been stopped, split tick_nohz_stop_sched_tick() into two separate routines, one computing the time to the next timer event and the other simply stopping the tick when the time to the next timer event is known. Prepare these two routines to be called separately, as one of them will be called by the idle governor in the cpuidle_select() code path after subsequent changes. Update the former callers of tick_nohz_stop_sched_tick() to use the new routines, tick_nohz_next_event() and tick_nohz_stop_tick(), instead of it and move the updates of the sleep_length field in struct tick_sched into __tick_nohz_idle_stop_tick() as it doesn't need to be updated anywhere else. There should be no intentional visible changes in functionality resulting from this change. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions