This series should address most reviews from Peterz in v4:
* Check that the remote tick doesn't come way too late. For that we
track the last time we called update_curr() with checking
tsk->se.exec_start which doesn't only account for ticks but also queue
and dequeue events.
* Add comment to explain why we use HZ as a delay
* Feed changelog with explanation about correctness assumptions on
calling rq::task_tick() remotely.
The last element is to enforce unbound workqueues to queue a work on
a CPU of the same node when the enqueuer is outside the unbound mask.
This will be sorted out seperately.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
sched/0hz-v5
HEAD: 62711eb7856882d443615f0ef0ba9518977b7abd
Thanks,
Frederic
---
Frederic Weisbecker (6):
sched: Rename init_rq_hrtick to hrtick_rq_init
nohz: Allow to check if remote CPU tick is stopped
sched/isolation: Isolate workqueues when "nohz_full=" is set
sched/isolation: Residual 1Hz scheduler tick offload
sched/nohz: Remove the 1 Hz tick code
sched/isolation: Tick offload documentation
Documentation/admin-guide/kernel-parameters.txt | 6 +-
include/linux/sched/isolation.h | 1 +
include/linux/sched/nohz.h | 4 -
include/linux/tick.h | 2 +
kernel/sched/core.c | 116 ++++++++++++++++++------
kernel/sched/idle_task.c | 1 -
kernel/sched/isolation.c | 8 +-
kernel/sched/sched.h | 13 +--
kernel/time/tick-sched.c | 13 +--
kernel/workqueue.c | 3 +-
10 files changed, 115 insertions(+), 52 deletions(-)
