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>,
	Andrew Morton <akpm@linux-foundation.org>,
	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] printk: Support for full dynticks mode
Date: Tue, 5 Feb 2013 13:13:54 +0100	[thread overview]
Message-ID: <20130205121354.GC21455@gmail.com> (raw)
In-Reply-To: <1360025478-32741-1-git-send-email-fweisbec@gmail.com>


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

> Ingo,
> 
> Please pull the support for full dynticks idle mode in printk that
> can be found at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> 	nohz/printk-v9
> 
> nohz/printk-v8 was the tree that I proposed to Linus. It has been left unpulled
> though and we got no news from him but the tree has stayed untouched since then,
> waiting in -next without any issue.
> 
> Part of nohz/printk-v8 is now in tip:irq/core, and this pull request contains
> the rest. I could simply propose you the old branch but since there is a tiny
> conflict with another recent commit in tip:irq/core, I just made a new branch
> that contains tip:irq/core with nohz/printk-v8 merged inside which deals
> with the conflict.
> 
> Thanks.
> ---
> 
> Frederic Weisbecker (5):
>       nohz: Add API to check tick state
>       irq_work: Don't stop the tick with pending works
>       irq_work: Make self-IPIs optable
>       printk: Wake up klogd using irq_work
>       Merge branch 'nohz/printk-v8' into irq/core
> 
> Steven Rostedt (2):
>       irq_work: Flush work on CPU_DYING
>       irq_work: Warn if there's still work on cpu_down
> 
>  include/linux/irq_work.h |   20 ++++++++
>  include/linux/printk.h   |    3 -
>  include/linux/tick.h     |   17 +++++++-
>  init/Kconfig             |    1 +
>  kernel/irq_work.c        |  112 +++++++++++++++++++++++++++++++++++-----------
>  kernel/printk.c          |   36 ++++++++-------
>  kernel/time/tick-sched.c |    7 ++-
>  kernel/timer.c           |    1 -
>  8 files changed, 147 insertions(+), 50 deletions(-)

Pulled, thanks Frederic!

	Ingo

      parent reply	other threads:[~2013-02-05 12:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05  0:51 [GIT PULL] printk: Support for full dynticks mode Frederic Weisbecker
2013-02-05  1:20 ` Andrew Morton
2013-02-05  1:22   ` Steven Rostedt
2013-02-05  1:37   ` Frederic Weisbecker
2013-02-05  2:09     ` Andrew Morton
2013-02-05  2:42       ` Steven Rostedt
2013-02-05  4:04         ` Andrew Morton
2013-02-05 12:05           ` Ingo Molnar
2013-02-05  3:14       ` Steven Rostedt
2013-02-05  3:19         ` Frederic Weisbecker
2013-02-05  3:24           ` Steven Rostedt
2013-02-05  3:29             ` Steven Rostedt
2013-02-05 12:13 ` 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=20130205121354.GC21455@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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