From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, gilad@codefidence.com
Cc: kvm-devel@lists.sourceforge.net, chrisw@sous-sol.org, gcosta@redhat.com
Subject: Re: [Qemu-devel] [PATCH] use a thread id variable
Date: Sun, 09 Mar 2008 10:12:40 -0600 (MDT) [thread overview]
Message-ID: <20080309.101240.1782788363.imp@bsdimp.com> (raw)
In-Reply-To: <47D3F9AF.2030408@codefidence.com>
In message: <47D3F9AF.2030408@codefidence.com>
Gilad Ben-Yossef <gilad@codefidence.com> writes:
: > What you're supposed to do with pthreads in general is use pthread_self().
:
: Unfortunately, AFAIK the opaque handle that pthread_self() returns is
: not quite meaningless outside of the process whereas what the non
: standard gettid() returns can actually be used to identify a thread from
: "outside" the process, like the shell.
gettid() is also non-standard. If you want to interact with a thread,
you gotta use pthread_self() if you want your code to be portable.
Warner
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
WARNING: multiple messages have this Message-ID (diff)
From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, gilad@codefidence.com
Cc: kvm-devel@lists.sourceforge.net, glommer@gmail.com,
chrisw@sous-sol.org, gcosta@redhat.com
Subject: Re: [Qemu-devel] [PATCH] use a thread id variable
Date: Sun, 09 Mar 2008 10:12:40 -0600 (MDT) [thread overview]
Message-ID: <20080309.101240.1782788363.imp@bsdimp.com> (raw)
In-Reply-To: <47D3F9AF.2030408@codefidence.com>
In message: <47D3F9AF.2030408@codefidence.com>
Gilad Ben-Yossef <gilad@codefidence.com> writes:
: > What you're supposed to do with pthreads in general is use pthread_self().
:
: Unfortunately, AFAIK the opaque handle that pthread_self() returns is
: not quite meaningless outside of the process whereas what the non
: standard gettid() returns can actually be used to identify a thread from
: "outside" the process, like the shell.
gettid() is also non-standard. If you want to interact with a thread,
you gotta use pthread_self() if you want your code to be portable.
Warner
next prev parent reply other threads:[~2008-03-09 16:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 20:01 [PATCH 0/3] Expose thread id through info cpus Glauber Costa
2008-03-05 20:01 ` [Qemu-devel] " Glauber Costa
2008-03-05 20:01 ` [PATCH] use a thread id variable Glauber Costa
2008-03-05 20:01 ` [Qemu-devel] " Glauber Costa
2008-03-05 20:01 ` [PATCH] augment info cpus Glauber Costa
2008-03-05 20:01 ` [Qemu-devel] " Glauber Costa
2008-03-05 20:01 ` [PATCH] KVM: use actual thread id for vcpus Glauber Costa
2008-03-05 20:01 ` [Qemu-devel] " Glauber Costa
2008-03-09 9:26 ` [Qemu-devel] [PATCH] use a thread id variable Gilad Ben-Yossef
2008-03-09 9:26 ` Gilad Ben-Yossef
2008-03-09 11:58 ` Jamie Lokier
2008-03-09 11:58 ` Jamie Lokier
2008-03-09 14:52 ` Gilad Ben-Yossef
2008-03-09 14:52 ` Gilad Ben-Yossef
2008-03-09 16:12 ` M. Warner Losh [this message]
2008-03-09 16:12 ` M. Warner Losh
2008-03-17 17:55 ` Glauber Costa
2008-03-17 17:55 ` Glauber Costa
2008-03-09 16:09 ` M. Warner Losh
2008-03-09 16:09 ` M. Warner Losh
2008-03-09 20:01 ` Jamie Lokier
2008-03-09 20:01 ` Jamie Lokier
2008-03-09 16:23 ` Daniel P. Berrange
2008-03-09 16:23 ` [kvm-devel] " Daniel P. Berrange
2008-03-05 20:07 ` [PATCH 0/3] Expose thread id through info cpus Glauber Costa
2008-03-05 20:07 ` [Qemu-devel] " Glauber Costa
2008-03-06 6:55 ` Avi Kivity
2008-03-06 6:55 ` [Qemu-devel] " Avi Kivity
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=20080309.101240.1782788363.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=chrisw@sous-sol.org \
--cc=gcosta@redhat.com \
--cc=gilad@codefidence.com \
--cc=kvm-devel@lists.sourceforge.net \
--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.