public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	a.p.zijlstra@chello.nl, tglx@linutronix.de
Subject: [GIT RFC PULL] RCU changes for 2.6.35
Date: Fri, 7 May 2010 14:22:20 -0700	[thread overview]
Message-ID: <20100507212220.GA10465@linux.vnet.ibm.com> (raw)

Hello, Ingo,

Here is the first installment of RCU changes for 2.6.35.  These commits
are based on top of the rcu/urgent set sent yesterday.  If you would rather
rcu/urgent be merged into tip/core/rcu and then this set based on top of
that, or some other arrangement, please let me know.

git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/next

There are two more sets of commits queued:

o	Mathieu's debugobjects changes.  These need to be reworked in
	order to coordinate with other maintainer trees, and also to
	get the relevant Acked-by:s.  This will eventually apply in
	three stages: (1) add new RCU APIs, (2) apply these APIs into
	various trees, and (3) remove old RCU APIs.

o	Arnd's "sparse" checks.  These require a quadruple-action approach:
	(1) add a new RCU API member rcu_dereference_index_check(),
	(2) a couple of commits must be accepted into maintainer trees
	(networking, vfs, and mce), (3) a pair of RCU-infrastructure
	patches, and finally (4) a number of patches to apply __rcu
	attributes to various trees.

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

             reply	other threads:[~2010-05-07 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 21:22 Paul E. McKenney [this message]
2010-05-08  8:34 ` [GIT RFC PULL] RCU changes for 2.6.35 Ingo Molnar
2010-05-08 15:10   ` Paul E. McKenney
2010-05-08 16:10     ` Ingo Molnar

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=20100507212220.GA10465@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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