public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Chris Metcalf <cmetcalf@tilera.com>,
	Christoph Lameter <cl@linux.com>,
	Geoff Levand <geoff@infradead.org>,
	Gilad Ben Yossef <gilad@benyossef.com>,
	Hakan Akkan <hakanakkan@gmail.com>,
	Kevin Hilman <khilman@linaro.org>,
	Li Zhong <zhong@linux.vnet.ibm.com>,
	Oleg Nesterov <oleg@redhat.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL v2] nohz: Posix cpu timers handling on full dynticks
Date: Sun, 21 Apr 2013 11:26:52 +0200	[thread overview]
Message-ID: <20130421092652.GA10292@gmail.com> (raw)
In-Reply-To: <1366383100-17053-1-git-send-email-fweisbec@gmail.com>


* Frederic Weisbecker <fweisbec@gmail.com> wrote:

> 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(-)

Pulled, thanks Frederic!

	Ingo

      parent reply	other threads:[~2013-04-21  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 14:51 [GIT PULL v2] nohz: Posix cpu timers handling on full dynticks Frederic Weisbecker
2013-04-19 14:51 ` [PATCH 1/3] nohz: New APIs to re-evaluate the tick on full dynticks CPUs Frederic Weisbecker
2013-04-19 14:51 ` [PATCH 2/3] posix_timers: Kick full dynticks CPUs when a posix cpu timer is armed Frederic Weisbecker
2013-04-19 14:51 ` [PATCH 3/3] posix_timers: New API to prevent from stopping the tick when timers are running Frederic Weisbecker
2013-04-21  9:26 ` Ingo Molnar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130421092652.GA10292@gmail.com \
    --to=mingo@kernel.org \
    --cc=cl@linux.com \
    --cc=cmetcalf@tilera.com \
    --cc=fweisbec@gmail.com \
    --cc=geoff@infradead.org \
    --cc=gilad@benyossef.com \
    --cc=hakanakkan@gmail.com \
    --cc=khilman@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=zhong@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox