From: "Alex Bennée" <alex.bennee@linaro.org>
To: stefanha@redhat.com, pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Peter Crosthwaite" <crosthwaite.peter@gmail.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH] cpus: make qemu_mutex_iothread_locked() understand co-routines
Date: Fri, 21 Oct 2016 12:54:42 +0100 [thread overview]
Message-ID: <20161021115442.18420-1-alex.bennee@linaro.org> (raw)
There is a slight wart when checking for the state of the BQL when using
GThread base co-routines (which we keep for ThreadSanitizer runs). While
the main-loop holds the BQL it is suspended until the co-routine
completes however the co-routines run in a separate thread so checking
the TLS variable could be wrong.
We fix this by expanding the check to include qemu_in_coroutine() for
GThread based builds. As it is not used for production builds I'm not
overly worried about any performance impact which should be negligible
anyway.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Cc: Stefan Hajnoczi <stefanha@redhat.com>
---
configure | 3 +++
cpus.c | 13 +++++++++++++
2 files changed, 16 insertions(+)
diff --git a/configure b/configure
index 91a14c1..97b89fb 100755
--- a/configure
+++ b/configure
@@ -5461,6 +5461,9 @@ if test "$rbd" = "yes" ; then
fi
echo "CONFIG_COROUTINE_BACKEND=$coroutine" >> $config_host_mak
+if test "$coroutine" = "gthread" ; then
+ echo "CONFIG_COROUTINE_GTHREAD=1" >> $config_host_mak
+fi
if test "$coroutine_pool" = "yes" ; then
echo "CONFIG_COROUTINE_POOL=1" >> $config_host_mak
else
diff --git a/cpus.c b/cpus.c
index 0c18a9f..a3e189a 100644
--- a/cpus.c
+++ b/cpus.c
@@ -49,6 +49,10 @@
#include "hw/nmi.h"
#include "sysemu/replay.h"
+#ifdef CONFIG_COROUTINE_GTHREAD
+#include "qemu/coroutine.h"
+#endif
+
#ifndef _WIN32
#include "qemu/compatfd.h"
#endif
@@ -1422,9 +1426,18 @@ bool qemu_in_vcpu_thread(void)
static __thread bool iothread_locked = false;
+/*
+ * There is a slight wart when using gthread based co-routines. Here
+ * the BQL is held by the main-thread which is suspended until the
+ * co-routines complete.
+ */
bool qemu_mutex_iothread_locked(void)
{
+#ifdef CONFIG_COROUTINE_GTHREAD
+ return iothread_locked || qemu_in_coroutine();
+#else
return iothread_locked;
+#endif
}
void qemu_mutex_lock_iothread(void)
--
2.9.3
next reply other threads:[~2016-10-21 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 11:54 Alex Bennée [this message]
2016-11-01 15:04 ` [Qemu-devel] [PATCH] cpus: make qemu_mutex_iothread_locked() understand co-routines Paolo Bonzini
2016-11-01 16:21 ` Alex Bennée
2016-11-02 14:06 ` Stefan Hajnoczi
2016-11-02 14:55 ` Alex Bennée
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=20161021115442.18420-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=crosthwaite.peter@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@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).