[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1366383100-17053-1-git-send-email-fweisbec@gmail.com>
Date:	Fri, 19 Apr 2013 16:51:37 +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>,
	Chris Metcalf <cmetcalf@...era.com>,
	Christoph Lameter <cl@...ux.com>,
	Geoff Levand <geoff@...radead.org>,
	Gilad Ben Yossef <gilad@...yossef.com>,
	Hakan Akkan <hakanakkan@...il.com>,
	Kevin Hilman <khilman@...aro.org>,
	Li Zhong <zhong@...ux.vnet.ibm.com>,
	Oleg Nesterov <oleg@...hat.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: [GIT PULL v2] nohz: Posix cpu timers handling on full dynticks
Ingo,
Please pull this second version of the dynticks handling of posix cpu
timers from:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
	timers/nohz-posix-timers-v2
This fixes an issue with a race between run_posix_cpu_timers() and full
dynticks CPUs that we found while discussing a patch with Olivier Langlois.
As a bonus, it also provides the other side of posix cpu timers handling
in dynticks with the new helper to check before stopping the tick.
Thanks.
Frederic Weisbecker (3):
  nohz: New APIs to re-evaluate the tick on full dynticks CPUs
  posix_timers: Kick full dynticks CPUs when a posix cpu timer is armed
  posix_timers: New API to prevent from stopping the tick when timers
    are running
 include/linux/posix-timers.h |    2 +
 include/linux/tick.h         |    4 ++
 kernel/posix-cpu-timers.c    |   76 +++++++++++++++++++++++++++++++++---------
 kernel/time/Kconfig          |    1 +
 kernel/time/tick-sched.c     |   51 ++++++++++++++++++++++++++++
 5 files changed, 118 insertions(+), 16 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
 
