Hi Ingo,
So with this we are mostly done with the RCU and timekeeping sides.
The interface is still a bit spartan:
* Need to keep the boot CPU outside full dynticks range.
* Need to have nohz_full= be a subset of rcu_nocbs=
Note that none of this is thought to be fixed on the rock. It's
just a KISS interface settlement so that we can focus on the
central things.
These constraints will likely be removed in the future.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
timers/nohz
HEAD: da922312f6980cb9214a64f7303f6cb3cf93626f
Thanks.
Frederic Weisbecker (3):
nohz: Force boot CPU outside full dynticks range
nohz: Ensure full dynticks CPUs are RCU nocbs
nohz: New option to default all CPUs in full dynticks range
Documentation/kernel-parameters.txt | 6 ++-
include/linux/rcupdate.h | 7 +++
include/linux/tick.h | 2 +
init/main.c | 1 +
kernel/rcutree.c | 6 +-
kernel/rcutree.h | 1 -
kernel/rcutree_plugin.h | 13 ++----
kernel/time/Kconfig | 10 +++++
kernel/time/tick-sched.c | 77 ++++++++++++++++++----------------
9 files changed, 72 insertions(+), 51 deletions(-)
--
1.7.5.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
