mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	a.p.zijlstra@chello.nl, tglx@linutronix.de
Subject: Re: [GIT PULL] RCU changes for 2.6.35
Date: Tue, 11 May 2010 09:15:26 +0200	[thread overview]
Message-ID: <20100511071526.GA10421@elte.hu> (raw)
In-Reply-To: <20100510203750.GA12918@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> Hello, Ingo,
> 
> Here are the first installment of RCU changes for 2.6.35, this time
> rebased to 2.6.34-rc7.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/next
> 
> As noted earlier, Mathieu's debugobjects changes and Arnd's "sparse"
> checks are also in the works.
> 
> 							Thanx, Paul
> 
> ------------------>
>  Lai Jiangshan (4)
> 	 rcu: optionally leave lockdep enabled after RCU lockdep splat
> 	 rcu: make dead code really dead
> 	 rcu: move some code from macro to function
> 	 rcu: ignore offline CPUs in last non-dyntick-idle CPU check
> 
>  Paul E. McKenney (17)
> 	 rcu: substitute set_need_resched for sending resched IPIs
> 	 rcu: Fix bogus CONFIG_PROVE_LOCKING in comments to reflect reality.
> 	 rcu: fix now-bogus rcu_scheduler_active comments.
> 	 rcu: shrink rcutiny by making synchronize_rcu_bh() be inline
> 	 rcu: rename rcutiny rcu_ctrlblk to rcu_sched_ctrlblk
> 	 rcu: refactor RCU's context-switch handling
> 	 rcu: slim down rcutiny by removing rcu_scheduler_active and friends
> 	 rcu: enable CPU_STALL_VERBOSE by default
> 	 rcu: disable CPU stall warnings upon panic
> 	 rcu: print boot-time console messages if RCU configs out of ordinary
> 	 rcu: improve RCU CPU stall-warning messages
> 	 rcu: permit discontiguous cpu_possible_mask CPU numbering
> 	 rcu: reduce the number of spurious RCU_SOFTIRQ invocations
> 	 rcu: improve the RCU CPU-stall warning documentation
> 	 rcu: make SRCU usable in modules
> 	 rcu: RCU_FAST_NO_HZ must check RCU dyntick state
> 	 rcu: fix build bug in RCU_FAST_NO_HZ builds
> 
>  Documentation/RCU/stallwarn.txt |   94 ++++++++++++++++++++++-------
>  Documentation/RCU/trace.txt     |   35 +++++------
>  include/linux/rcupdate.h        |   42 +++++++------
>  include/linux/rcutiny.h         |   29 ++++++++-
>  include/linux/rcutree.h         |    6 +
>  include/linux/srcu.h            |    6 +
>  kernel/lockdep.c                |    3 
>  kernel/rcupdate.c               |   19 -----
>  kernel/rcutiny.c                |   29 +++++----
>  kernel/rcutiny_plugin.h         |   39 ++++++++++++
>  kernel/rcutree.c                |  127 ++++++++++++++++++++++++++++------------
>  kernel/rcutree.h                |    2 
>  kernel/rcutree_plugin.h         |   67 ++++++++++++++++++---
>  kernel/rcutree_trace.c          |    4 -
>  kernel/sched.c                  |    2 
>  kernel/softirq.c                |    2 
>  lib/Kconfig.debug               |   14 ++++
>  17 files changed, 381 insertions(+), 139 deletions(-)

Pulled, thanks a lot Paul!

	Ingo

      reply	other threads:[~2010-05-11  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 20:37 Paul E. McKenney
2010-05-11  7:15 ` 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=20100511071526.GA10421@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --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

all inboxes | Powered by JetHome®