[PATCH 0/9] nohz: Tick dependency mask v4

From: Frederic Weisbecker
Date: Mon Dec 14 2015 - 13:38:45 EST


Thanks to reviews on v3, here are the following changes:

* Let arch override fetch_or() (Chris)
* Implement wide kick on top of irq work (Peterz)
* Provide explicit task and signal tick dependency APIs
* Better document the task and signal dependencies (Peterz)
* Better document all the new APIs
* Provide off cases
* Convert nohz tracing to use enum codes (Peterz)
* Fix race in perf (Chris and Peterz)
* Avoid remote irq_work if in NMI (Chris)
* Deduce fifo tasks from total_rt - total_rr (Peterz)
* Spelling fixes (Chris)

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
timers/core-v6

HEAD: a3334ec8452d9113bfe6b94a3ddede54f68b7300

Thanks,
Frederic
---

Frederic Weisbecker (9):
atomic: Export fetch_or()
nohz: Implement wide kick on top of irq work
nohz: New tick dependency mask
nohz: Use enum code for tick stop failure tracing message
perf: Migrate perf to use new tick dependency mask model
sched: Account rr tasks
sched: Migrate sched to use new tick dependency mask model
posix-cpu-timers: Migrate to use new tick dependency mask model
sched-clock: Migrate to use new tick dependency mask model


include/linux/atomic.h | 21 +++++
include/linux/perf_event.h | 6 --
include/linux/posix-timers.h | 3 -
include/linux/sched.h | 11 ++-
include/linux/tick.h | 44 ++++++++++-
include/trace/events/timer.h | 36 +++++++--
kernel/events/core.c | 65 +++++++++++----
kernel/sched/clock.c | 5 ++
kernel/sched/core.c | 50 +++++-------
kernel/sched/rt.c | 16 ++++
kernel/sched/sched.h | 48 +++++++----
kernel/time/posix-cpu-timers.c | 52 +++---------
kernel/time/tick-sched.c | 175 ++++++++++++++++++++++++++++++++---------
kernel/time/tick-sched.h | 1 +
14 files changed, 372 insertions(+), 161 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/