From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.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>,
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] nohz: More Kconfig and Rcu improvements
Date: Tue, 16 Apr 2013 10:46:13 +0200 [thread overview]
Message-ID: <20130416084613.GA7480@gmail.com> (raw)
In-Reply-To: <1366060220-20271-1-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Ingo,
>
> Please pull the latest timers/nohz branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/nohz
>
> HEAD: 65d798f0f9339ae2c4ebe9480e3260b33382a584
>
> This fixes some of the issues you've reported. There is still the
> dependency on CONFIG_VIRT_CPU_ACCOUNTING_GEN to fix, probably in
> the Kconfig side. Stay tuned.
>
> Thanks.
>
> ---
> Frederic Weisbecker (4):
> nohz: Fix old dynticks idle Kconfig backward compatibility
> nohz: Switch from "extended nohz" to "full nohz" based naming
> nohz: Align periodic tick Kconfig with other choices' naming
> convention
> nohz: Improve a bit the full dynticks Kconfig documentation
>
> Paul E. McKenney (1):
> rcu: Kick adaptive-ticks CPUs that are holding up RCU grace periods
>
> Documentation/kernel-parameters.txt | 4 +-
> include/linux/tick.h | 6 ++--
> kernel/rcutree.c | 10 ++++++
> kernel/rcutree.h | 1 +
> kernel/rcutree_plugin.h | 18 +++++++++++
> kernel/sched/core.c | 6 ++--
> kernel/time/Kconfig | 26 ++++++++++------
> kernel/time/tick-broadcast.c | 2 +-
> kernel/time/tick-common.c | 2 +-
> kernel/time/tick-sched.c | 54 +++++++++++++++++-----------------
> 10 files changed, 82 insertions(+), 47 deletions(-)
Pulled, thanks Frederic!
Ingo
prev parent reply other threads:[~2013-04-16 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 21:10 [GIT PULL] nohz: More Kconfig and Rcu improvements Frederic Weisbecker
2013-04-15 21:10 ` [PATCH 1/5] nohz: Fix old dynticks idle Kconfig backward compatibility Frederic Weisbecker
2013-04-15 21:10 ` [PATCH 2/5] nohz: Switch from "extended nohz" to "full nohz" based naming Frederic Weisbecker
2013-04-15 21:10 ` [PATCH 3/5] nohz: Align periodic tick Kconfig with other choices' naming convention Frederic Weisbecker
2013-04-15 21:10 ` [PATCH 4/5] nohz: Improve a bit the full dynticks Kconfig documentation Frederic Weisbecker
2013-04-15 21:10 ` [PATCH 5/5] rcu: Kick adaptive-ticks CPUs that are holding up RCU grace periods Frederic Weisbecker
2013-04-16 8:46 ` 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=20130416084613.GA7480@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=josh@joshtriplett.org \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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