From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.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 RFC v2 tip/core/rcu 0/2] Make RCU synchronous grace periods work throughout boot
Date: Sat, 14 Jan 2017 00:45:30 -0800 [thread overview]
Message-ID: <20170114084530.GA17256@linux.vnet.ibm.com> (raw)
Hello!
This series fixes a regression in v4.9 where code relied on RCU synchronous
grace periods working between the time that the scheduler spawned the
first task and RCU finished spawning all of its tasks. This series makes
RCU able to handle synchronous grace periods throughout boot. Please
see the second patch's commit log for more details.
The patches are as follows:
1. Remove cond_resched() from Tiny synchronize_sched(), thus allowing
Tiny RCU's synchronize_sched() to be used throughout boot
without annoying splats.
2. Make RCU's expedited synchronous grace periods work throughout
boot, and promote non-expedited grace periods to expedited
grace periods during boot from the time that the scheduler
spawns the first task until after RCU has spawned all of its
kthreads.
Changes from v1:
o Added the fix for Tiny RCU.
o Applied Borislav Petkov's feedback for Tree RCU.
o Added a bunch of Tested-by lines.
Thanx, Paul
------------------------------------------------------------------------
include/linux/rcupdate.h | 4 +++
kernel/rcu/rcu.h | 1
kernel/rcu/tiny.c | 4 ---
kernel/rcu/tiny_plugin.h | 9 ++++++--
kernel/rcu/tree.c | 33 ++++++++++++++++++-----------
kernel/rcu/tree_exp.h | 52 +++++++++++++++++++++++++++++++++++++----------
kernel/rcu/tree_plugin.h | 2 -
kernel/rcu/update.c | 38 +++++++++++++++++++++++++++-------
8 files changed, 104 insertions(+), 39 deletions(-)
reply other threads:[~2017-01-14 11:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170114084530.GA17256@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=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--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 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.