From: Scott Wood <swood@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
"Paul E . McKenney" <paulmck@linux.ibm.com>,
Joel Fernandes <joel@joelfernandes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Clark Williams <williams@redhat.com>
Subject: [PATCH RT v3 0/5] RCU fixes
Date: Wed, 11 Sep 2019 17:57:24 +0100 [thread overview]
Message-ID: <20190911165729.11178-1-swood@redhat.com> (raw)
With these patches, rcutorture works on PREEMPT_RT_FULL.
Scott Wood (5):
rcu: Acquire RCU lock when disabling BHs
sched: Rename sleeping_lock to rt_invol_sleep
sched: migrate_dis/enable: Use rt_invol_sleep
rcu: Disable use_softirq on PREEMPT_RT
rcutorture: Avoid problematic critical section nesting
include/linux/rcupdate.h | 40 +++++++++++++++----
include/linux/sched.h | 19 ++++-----
kernel/cpu.c | 2 +
kernel/locking/rtmutex.c | 14 +++----
kernel/locking/rwlock-rt.c | 16 ++++----
kernel/rcu/rcutorture.c | 96 +++++++++++++++++++++++++++++++++++++++-------
kernel/rcu/tree.c | 9 ++++-
kernel/rcu/tree_plugin.h | 8 ++--
kernel/sched/core.c | 4 ++
kernel/softirq.c | 14 +++++--
kernel/time/hrtimer.c | 4 +-
11 files changed, 168 insertions(+), 58 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-09-11 16:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 16:57 Scott Wood [this message]
2019-09-11 16:57 ` [PATCH RT v3 1/5] rcu: Acquire RCU lock when disabling BHs Scott Wood
2019-09-12 22:09 ` Joel Fernandes
2019-09-17 7:44 ` Sebastian Andrzej Siewior
2019-09-17 14:06 ` Scott Wood
2019-09-17 14:42 ` Sebastian Andrzej Siewior
2019-09-17 16:12 ` Scott Wood
2019-09-23 16:41 ` Sebastian Andrzej Siewior
2019-09-11 16:57 ` [PATCH RT v3 2/5] sched: Rename sleeping_lock to rt_invol_sleep Scott Wood
2019-09-17 7:52 ` Sebastian Andrzej Siewior
2019-09-11 16:57 ` [PATCH RT v3 3/5] sched: migrate_dis/enable: Use rt_invol_sleep Scott Wood
2019-09-17 7:59 ` Sebastian Andrzej Siewior
2019-09-17 14:06 ` Scott Wood
2019-09-23 16:59 ` Scott Wood
2019-09-23 17:52 ` Sebastian Andrzej Siewior
2019-09-24 11:21 ` Sebastian Andrzej Siewior
2019-09-24 13:53 ` Scott Wood
2019-09-24 15:25 ` Sebastian Andrzej Siewior
2019-09-24 15:47 ` Scott Wood
2019-09-24 16:05 ` Sebastian Andrzej Siewior
2019-09-24 16:35 ` Scott Wood
2019-10-04 16:45 ` Sebastian Andrzej Siewior
2019-09-11 16:57 ` [PATCH RT v3 4/5] rcu: Disable use_softirq on PREEMPT_RT Scott Wood
2019-09-12 21:38 ` Joel Fernandes
2019-09-12 22:19 ` Joel Fernandes
2019-09-17 9:31 ` Sebastian Andrzej Siewior
2019-09-17 14:08 ` Scott Wood
2019-09-11 16:57 ` [PATCH RT v3 5/5] rcutorture: Avoid problematic critical section nesting on RT Scott Wood
2019-09-12 22:17 ` Joel Fernandes
2019-09-16 16:55 ` Scott Wood
2019-09-17 10:07 ` Sebastian Andrzej Siewior
2019-09-17 14:36 ` Scott Wood
2019-09-17 14:50 ` Sebastian Andrzej Siewior
2019-09-17 16:32 ` Scott Wood
2019-09-23 16:25 ` Sebastian Andrzej Siewior
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=20190911165729.11178-1-swood@redhat.com \
--to=swood@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).