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 PULL] rcu: infrastructure for debugobjects checking
Date: Thu, 13 May 2010 16:06:51 -0700 [thread overview]
Message-ID: <20100513230651.GA24426@linux.vnet.ibm.com> (raw)
Hello, Ingo,
Here are the first three commits from Mathieu's debugobjects series
(http://lwn.net/Articles/387344/). The first two provide the debugobjects
infrastructure and the RCU APIs, and the third applies these APIs to
the RCU implementation itself.
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/next
Once these three reach mainline, I will submit the next six commits
to their respective trees (powerpc, block, staging, fs, mm, and selinux).
The maintainers have been CCed on the the earlier LKML patchsets.
Once these six commits reach mainline, I will send you a pull request
for the remaining two commits.
Then on to Arnd's "sparse" checks, which are still being refined.
Thanx, Paul
------------------>
Mathieu Desnoyers (2)
Debugobjects transition check
rcu head introduce rcu head init on stack
Paul E. McKenney (1)
rcu: remove all rcu head initializations, except on_stack initializations
include/linux/debugobjects.h | 11 ++++++++
include/linux/init_task.h | 1 -
include/linux/rcupdate.h | 8 +++++
kernel/rcutiny.c | 6 ++++
kernel/rcutorture.c | 2 +
kernel/rcutree.c | 4 +++
kernel/rcutree_plugin.h | 2 +
lib/debugobjects.c | 59 +++++++++++++++++++++++++++++++++++++++--
8 files changed, 89 insertions(+), 4 deletions(-)
next reply other threads:[~2010-05-13 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 23:06 Paul E. McKenney [this message]
2010-05-14 6:15 ` [GIT PULL] rcu: infrastructure for debugobjects checking 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=20100513230651.GA24426@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.