[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1339433602-26836-1-git-send-email-fweisbec@gmail.com>
Date: Mon, 11 Jun 2012 18:53:17 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Alessio Igor Bogani <abogani@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Avi Kivity <avi@...hat.com>,
Chris Metcalf <cmetcalf@...era.com>,
Christoph Lameter <cl@...ux.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Geoff Levand <geoff@...radead.org>,
Gilad Ben Yossef <gilad@...yossef.com>,
Hakan Akkan <hakanakkan@...il.com>,
Kevin Hilman <khilman@...com>,
Max Krasnyansky <maxk@...lcomm.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Stephen Hemminger <shemminger@...tta.com>,
Steven Rostedt <rostedt@...dmis.org>,
Sven-Thorsten Dietrich <thebigcorporation@...il.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: [GIT PULL] nohz: Generalize nohz APIs for adaptive tickless
Ingo,
As per your suggestion I think it may be time to start a tree in -tip
and iterate incrementally there with what looks to me like the
uncontroversial bits of nohz cpusets.
This pile does the preparatory work to make the nohz API idle-agnostic
so that we are able to stop and restart the tick from non-idle places.
If you're fine with it, it's pullable there:
git://github.com/fweisbec/linux-dynticks.git
nohz-for-tip
Frederic Weisbecker (5):
nohz: Separate idle sleeping time accounting from nohz logic
nohz: Make nohz API agnostic against idle ticks cputime accounting
nohz: Rename ts->idle_tick to ts->last_tick
nohz: Move ts->idle_calls incrementation into strict idle logic
nohz: Move next idle expiry time record into idle logic area
include/linux/tick.h | 8 +-
kernel/time/tick-sched.c | 191 ++++++++++++++++++++++++++--------------------
kernel/time/timer_list.c | 4 +-
3 files changed, 115 insertions(+), 88 deletions(-)
--
1.7.5.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists