From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 3/3] rcu: detect missing rcu_register_thread()
Date: Mon, 13 Jul 2015 13:31:05 +0200 [thread overview]
Message-ID: <1436787065-25095-4-git-send-email-pbonzini@redhat.com> (raw)
In-Reply-To: <1436787065-25095-1-git-send-email-pbonzini@redhat.com>
Use an "impossible" value for the .depth field in order to quickly
detect threads that have not registered themselves with the RCU
subsystem.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
include/qemu/rcu.h | 4 +++-
util/rcu.c | 18 ++++++++++++++++--
2 files changed, 19 insertions(+), 3 deletions(-)
diff --git a/include/qemu/rcu.h b/include/qemu/rcu.h
index 7df1e86..4facb35 100644
--- a/include/qemu/rcu.h
+++ b/include/qemu/rcu.h
@@ -82,7 +82,9 @@ static inline void rcu_read_lock(void)
struct rcu_reader_data *p_rcu_reader = &rcu_reader;
unsigned ctr;
- if (p_rcu_reader->depth++ > 0) {
+ p_rcu_reader->depth++;
+ assert(p_rcu_reader->depth >= 1);
+ if (p_rcu_reader->depth > 1) {
return;
}
diff --git a/util/rcu.c b/util/rcu.c
index 8830295..435cdbe 100644
--- a/util/rcu.c
+++ b/util/rcu.c
@@ -63,8 +63,11 @@ static inline int rcu_gp_ongoing(unsigned long *ctr)
/* Written to only by each individual reader. Read by both the reader and the
* writers.
+ *
+ * Initializing the depth to -1 causes an assertion failure on the first
+ * call to rcu_read_lock() if the thread does not call rcu_register_thread().
*/
-__thread struct rcu_reader_data rcu_reader;
+__thread struct rcu_reader_data rcu_reader = { .depth = -1 };
/* Protected by rcu_gp_lock. */
typedef QLIST_HEAD(, rcu_reader_data) ThreadList;
@@ -277,7 +280,12 @@ static void rcu_unregister_thread_notify(Notifier *n, void *data)
void rcu_register_thread(void)
{
- assert(rcu_reader.ctr == 0);
+ /* rcu_reader.depth is also used to detect whether the thread is
+ * registered.
+ */
+ assert(rcu_reader.depth == -1);
+ rcu_reader.depth = 0;
+
qemu_mutex_lock(&rcu_gp_lock);
QLIST_INSERT_HEAD(®istry, &rcu_reader, node);
qemu_mutex_unlock(&rcu_gp_lock);
@@ -288,6 +296,12 @@ void rcu_register_thread(void)
void rcu_unregister_thread(void)
{
+ /* Resetting the depth to -1 causes an assertion failure on the next
+ * call to rcu_read_lock().
+ */
+ assert(rcu_reader.depth == 0);
+ rcu_reader.depth = -1;
+
qemu_mutex_lock(&rcu_gp_lock);
QLIST_REMOVE(&rcu_reader, node);
qemu_mutex_unlock(&rcu_gp_lock);
--
2.4.3
next prev parent reply other threads:[~2015-07-13 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 11:31 [Qemu-devel] [PATCH 0/3] rcu: missing thread registration Paolo Bonzini
2015-07-13 11:31 ` [Qemu-devel] [PATCH 1/3] rcu: automatically unregister threads when they exit Paolo Bonzini
2015-07-13 11:31 ` [Qemu-devel] [PATCH 2/3] rcu: actually register threads that have RCU read-side critical sections Paolo Bonzini
2015-07-13 11:31 ` Paolo Bonzini [this message]
2015-07-14 3:36 ` [Qemu-devel] [PATCH 0/3] rcu: missing thread registration Fam Zheng
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=1436787065-25095-4-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).