From: Glauber Costa <glommer@redhat.com>
To: qemu-devel@nongnu.org
Cc: Glauber Costa <glommer@mothafucka.localdomain>, aliguori@us.ibm.com
Subject: [Qemu-devel] [PATCH 1/2] do proper cpu_self check
Date: Tue, 8 Sep 2009 16:13:39 -0400 [thread overview]
Message-ID: <1252440819-15923-1-git-send-email-glommer@redhat.com> (raw)
From: Glauber Costa <glommer@mothafucka.localdomain>
Currently, our check for qemu_cpu_self only checks if there is a cpu
currently in execution (represented by cpu_single_env being set). While
this might be okay for tcg, it is certainly not okay for kvm, since multiple
cpus might be executing.
Instead, I propose we use pthread primitives to test if the caller thread is
the same as env->thread.
For tcg, it will have the same semantics as before, since all CPUStates will
point to the same thread, and we'll only have one in execution at a time.
Signed-off-by: Glauber Costa <glommer@mothafucka.localdomain>
---
vl.c | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/vl.c b/vl.c
index a894285..604e996 100644
--- a/vl.c
+++ b/vl.c
@@ -3803,9 +3803,14 @@ void qemu_cpu_kick(void *_env)
qemu_thread_signal(env->thread, SIGUSR1);
}
-int qemu_cpu_self(void *env)
+int qemu_cpu_self(void *_env)
{
- return (cpu_single_env != NULL);
+ CPUState *env = _env;
+ QemuThread this;
+
+ qemu_thread_self(&this);
+
+ return qemu_thread_equal(&this, env->thread);
}
static void cpu_signal(int sig)
--
1.6.2.5
next reply other threads:[~2009-09-08 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 20:13 Glauber Costa [this message]
2009-09-08 20:08 ` [Qemu-devel] [PATCH 1/2] do proper cpu_self check Glauber Costa
-- strict thread matches above, loose matches on Subject: below --
2009-09-08 20:14 Glauber Costa
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=1252440819-15923-1-git-send-email-glommer@redhat.com \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@mothafucka.localdomain \
--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).