From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: julia@ni.com
Cc: linux-rt-users@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH RT 7/6] rcu: Do not include rtmutex_common.h unconditionally
Date: Mon, 9 Jul 2018 11:58:08 +0200 [thread overview]
Message-ID: <20180709095807.7lhflcfgy3yujt6z@linutronix.de> (raw)
In-Reply-To: <20180606133131.7747-1-bigeasy@linutronix.de>
[ upstream commit b88697810d7c1d102a529990f9071b0f14cfe6df ]
This commit adjusts include files and provides definitions in preparation
for suppressing lockdep false-positive ->boost_mtx complaints. Without
this preparation, architectures not supporting rt_mutex will get build
failures.
Reported-by: kbuild test robot <fengguang.wu@intel.com>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
Without this one we get build failures for RCU_BOOST=n. It would make
sense to apply this one before
[PATCH 6/6] rcu: Suppress lockdep false-positive ->boost_mtx complaints
kernel/rcu/tree_plugin.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
index ce069b37d961..d97eedd9c6d4 100644
--- a/kernel/rcu/tree_plugin.h
+++ b/kernel/rcu/tree_plugin.h
@@ -37,6 +37,7 @@
* This probably needs to be excluded from -rt builds.
*/
#define rt_mutex_owner(a) ({ WARN_ON_ONCE(1); NULL; })
+#define rt_mutex_futex_unlock(x) WARN_ON_ONCE(1)
#endif /* #else #ifdef CONFIG_RCU_BOOST */
@@ -828,8 +829,6 @@ static void rcu_cpu_kthread_setup(unsigned int cpu)
#ifdef CONFIG_RCU_BOOST
-#include "../locking/rtmutex_common.h"
-
#ifdef CONFIG_RCU_TRACE
static void rcu_initiate_boost_trace(struct rcu_node *rnp)
--
2.18.0
next prev parent reply other threads:[~2018-07-09 9:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 13:31 [v4.9 RT 0/6] futex backports Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 1/6] futex: Fix pi_state->owner serialization Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 2/6] futex: Fix more put_pi_state() vs. exit_pi_state_list() races Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 3/6] futex: Avoid violating the 10th rule of futex Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 4/6] futex: Fix OWNER_DEAD fixup Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 5/6] rtmutex: Make rt_mutex_futex_unlock() safe for irq-off callsites Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 6/6] rcu: Suppress lockdep false-positive ->boost_mtx complaints Sebastian Andrzej Siewior
2018-06-06 18:23 ` [v4.9 RT 0/6] futex backports Steven Rostedt
2018-06-12 17:53 ` Julia Cartwright
2018-06-15 16:11 ` Sebastian Andrzej Siewior
2018-07-09 9:58 ` Sebastian Andrzej Siewior [this message]
2018-07-10 16:53 ` [PATCH RT 8/6] sched, tracing: Fix trace_sched_pi_setprio() for deboosting 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=20180709095807.7lhflcfgy3yujt6z@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=julia@ni.com \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).