public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
	bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/4] Array-based RCU removals for 4.2
Date: Tue, 12 May 2015 14:18:14 -0700	[thread overview]
Message-ID: <20150512211814.GA31939@linux.vnet.ibm.com> (raw)

Hello!

This series removes the sole use of RCU-protected array indexes.
It turns out that this use is in x86 code, so smp_load_acquire() works
just as well, and this allows removing a troublesome aspect of the
RCU API.  This removal should in turn allow compilers to better grok RCU
dependency chains.  For example, expressions like (x-x), (x*0), and (x%1)
can result in valid array indexes, but cannot produce valid pointers.

1.	Make x86's MCE code use smp_load_acuire() and READ_ONCE() in
	place of the RCU API members intended to handle RCU-protected
	array indexes.

2.	Eliminates the RCU API members supporting RCU-protected array
	indexes, namely rcu_access_index() and rcu_dereference_index_check().

3.	Updates the RCU documentation to reflect #2 above.

4.	Makes one of the modified functions be static, courtesy of
	Fengguang Wu.

							Thanx, Paul

------------------------------------------------------------------------

 b/Documentation/RCU/arrayRCU.txt        |   20 ++++++++++--
 b/Documentation/RCU/lockdep.txt         |   10 ------
 b/Documentation/RCU/rcu_dereference.txt |   33 +++++++--------------
 b/Documentation/RCU/whatisRCU.txt       |    2 -
 b/arch/x86/kernel/cpu/mcheck/mce.c      |   15 +++++----
 b/include/linux/rcupdate.h              |   50 --------------------------------
 6 files changed, 37 insertions(+), 93 deletions(-)


             reply	other threads:[~2015-05-12 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 21:18 Paul E. McKenney [this message]
2015-05-12 21:18 ` [PATCH tip/core/rcu 1/4] mce: Stop using array-index-based RCU primitives Paul E. McKenney
2015-05-12 21:18   ` [PATCH tip/core/rcu 2/4] rcu: Eliminate " Paul E. McKenney
2015-05-13 13:08     ` Borislav Petkov
2015-05-14 20:27       ` Paul E. McKenney
2015-05-12 21:18   ` [PATCH tip/core/rcu 3/4] documentation: RCU-protected array indexes no longer supported Paul E. McKenney
2015-05-12 21:18   ` [PATCH tip/core/rcu 4/4] mce: mce_chrdev_write() can be static Paul E. McKenney
2015-05-13 10:31   ` [PATCH tip/core/rcu 1/4] mce: Stop using array-index-based RCU primitives Borislav Petkov
2015-05-13 12:51     ` 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=20150512211814.GA31939@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bobby.prani@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhart@linux.intel.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox