From: David Woodhouse <dwmw2@infradead.org>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH]ish NPTL support.
Date: Wed, 13 Dec 2006 17:32:03 +0000 [thread overview]
Message-ID: <1166031123.5253.745.camel@pmac.infradead.org> (raw)
In-Reply-To: <200612131722.17889.paul@codesourcery.com>
On Wed, 2006-12-13 at 17:22 +0000, Paul Brook wrote:
> I've a nasty feeling you're going to break the host libc if you do threading
> this way. One possibly solution is to use the pthreads API instead, and map
> everything onto that.
Qemu doesn't use the host's threading support, does it?
--
dwmw2
next prev parent reply other threads:[~2006-12-13 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 22:38 [Qemu-devel] [PATCH]ish NPTL support David Woodhouse
2006-12-13 16:02 ` Mulyadi Santosa
2006-12-13 17:01 ` David Woodhouse
2006-12-13 17:22 ` Paul Brook
2006-12-13 17:32 ` David Woodhouse [this message]
2006-12-13 17:42 ` Paul Brook
2006-12-13 17:50 ` David Woodhouse
2006-12-13 18:07 ` Paul Brook
2006-12-13 18:44 ` Fabrice Bellard
2006-12-14 2:16 ` Jamie Lokier
2006-12-16 13:26 ` David Woodhouse
2006-12-16 15:17 ` Paul Brook
2006-12-16 18:48 ` Jamie Lokier
2006-12-13 17:35 ` Thiemo Seufer
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=1166031123.5253.745.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=paul@codesourcery.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).