From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
josh@joshtriplett.org, dvhltc@us.ibm.com, niv@us.ibm.com,
tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com
Subject: [PATCH RFC tip/core/rcu 0/2] rcu: make RCU lockdep handle early boot in organized manner
Date: Mon, 1 Mar 2010 11:03:29 -0800 [thread overview]
Message-ID: <20100301190329.GA26892@linux.vnet.ibm.com> (raw)
Hello!
This patch set makes RCU lockdep handle early boot in an organized
manner:
1. Make rcu_read_lock_held(), rcu_read_lock_bh_held(),
rcu_read_lock_sched_held(), and rcu_dereference_check()
suppress complaints if !rcu_scheduler_active. The rationale
for this approach is that RCU grace periods are handled very
differently during early boot, and rcu_scheduler_active marks
the point that normal runtime RCU behavior starts.
2. Remove the !rcu_scheduler_active check from calls to
rcu_dereference_check(), because rcu_dereference_check() already
does the check in question.
Testing in progress, but want to get these out for review.
Thanx, Paul
------------------------------------------------------------------------
cgroup.h | 2 --
rcupdate.h | 27 +++++++++++++++++----------
2 files changed, 17 insertions(+), 12 deletions(-)
next reply other threads:[~2010-03-01 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 19:03 Paul E. McKenney [this message]
2010-03-01 19:03 ` [PATCH RFC tip/core/rcu 1/2] rcu: suppress RCU lockdep warnings during early boot Paul E. McKenney
2010-03-02 12:20 ` Ingo Molnar
2010-03-02 13:27 ` Paul E. McKenney
2010-03-02 14:12 ` Ingo Molnar
2010-03-02 14:55 ` Paul E. McKenney
2010-03-01 19:03 ` [PATCH RFC tip/core/rcu 2/2] rcu: revert 1883c79a: early boot now handled by lockdep-RCU Paul E. McKenney
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=20100301190329.GA26892@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.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 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.