From: Paolo Bonzini <bonzini@gnu.org>
To: Glauber Costa <glommer@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, avi@redhat.com
Subject: [Qemu-devel] Re: [PATCH v3] introduce on_vcpu
Date: Tue, 01 Sep 2009 02:55:28 +0200 [thread overview]
Message-ID: <4A9C7100.1020501@gnu.org> (raw)
In-Reply-To: <20090831113518.GD30340@mothafucka.localdomain>
On 08/31/2009 01:35 PM, Glauber Costa wrote:
> On Sat, Aug 29, 2009 at 02:22:27AM +0100, Jamie Lokier wrote:
>> Anthony Liguori wrote:
>>> Glauber Costa wrote:
>>> Since we already keep the tid in the vcpu structure, it seems to make
>>> more sense to ask "am I this vcpu thread" by doing gettid() == env->tid
>>> than by maintaining a new global tls variable.
>>
>> Note that a tls variable will be much faster than gettid(). Don't
>> know if you're talking about a hot path.
> just to be sure, TLS is not supported on all our linux target hosts, right?
I think it is.
~/devel/gcc/gcc pbonzini$ grep -l SYMBOL_REF_TLS_MODEL config/*/*.c
config/alpha/alpha.c
config/arm/arm.c
config/frv/frv.c
config/i386/i386.c
config/ia64/ia64.c
config/m68k/m68k.c
config/mips/mips.c
config/pa/pa.c
config/rs6000/rs6000.c
config/s390/s390.c
config/sh/sh.c
config/sparc/sparc.c
config/xtensa/xtensa.c
Paolo
prev parent reply other threads:[~2009-09-01 0:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 21:55 [Qemu-devel] [PATCH v3] introduce on_vcpu Glauber Costa
2009-08-27 17:15 ` [Qemu-devel] " Jan Kiszka
2009-08-27 17:40 ` Glauber Costa
2009-08-27 17:45 ` Jan Kiszka
2009-08-28 1:18 ` Glauber Costa
2009-08-28 1:38 ` Anthony Liguori
2009-08-28 1:58 ` Glauber Costa
2009-08-28 6:18 ` Gleb Natapov
2009-08-29 1:22 ` Jamie Lokier
2009-08-31 11:35 ` Glauber Costa
2009-08-31 12:04 ` Jamie Lokier
2009-08-31 12:14 ` Glauber Costa
2009-08-31 12:21 ` Jan Kiszka
2009-08-31 22:25 ` Jamie Lokier
2009-08-31 12:57 ` Glauber Costa
2009-09-01 0:55 ` Paolo Bonzini [this message]
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=4A9C7100.1020501@gnu.org \
--to=bonzini@gnu.org \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=jan.kiszka@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.