From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, efault@gmx.de,
peterz@infradead.org, josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com
Subject: [GIT PULL rcu/next] Additional RCU commit for 4.18
Date: Tue, 29 May 2018 10:35:18 -0700 [thread overview]
Message-ID: <20180529173518.GA6850@linux.vnet.ibm.com> (raw)
Hello, Ingo,
This additional v4.18 pull request contains a single commit that fell
through the cracks:
1. Provide early rcu_cpu_starting() callback for the benefit of the
x86/mtrr code, which needs RCU to be available on incoming CPUs
earlier than has been the case in the past.
http://lkml.kernel.org/r/20180525191802.GA7141@linux.vnet.ibm.com
All of these changes have been subjected to 0day Test Robot and -next
testing, and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo
for you to fetch changes up to f64c6013a2029316ea552f99823d116ee5f5f955:
rcu/x86: Provide early rcu_cpu_starting() callback (2018-05-22 16:12:26 -0700)
----------------------------------------------------------------
Peter Zijlstra (1):
rcu/x86: Provide early rcu_cpu_starting() callback
arch/x86/kernel/cpu/mtrr/main.c | 4 ++++
include/linux/rcupdate.h | 1 -
include/linux/rcutiny.h | 1 +
include/linux/rcutree.h | 1 +
kernel/rcu/tree.c | 9 +++++++++
5 files changed, 15 insertions(+), 1 deletion(-)
next reply other threads:[~2018-05-29 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 17:35 Paul E. McKenney [this message]
2018-05-30 5:56 ` [GIT PULL rcu/next] Additional RCU commit for 4.18 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=20180529173518.GA6850@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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