From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GuY7Y-0007eE-3h
	for qemu-devel@nongnu.org; Wed, 13 Dec 2006 12:42:20 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GuY7W-0007de-6t
	for qemu-devel@nongnu.org; Wed, 13 Dec 2006 12:42:19 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GuY7W-0007db-4G
	for qemu-devel@nongnu.org; Wed, 13 Dec 2006 12:42:18 -0500
Received: from [65.74.133.4] (helo=mail.codesourcery.com)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GuY7W-0004wd-0n
	for qemu-devel@nongnu.org; Wed, 13 Dec 2006 12:42:18 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH]ish NPTL support.
Date: Wed, 13 Dec 2006 17:42:11 +0000
References: <1165703896.5253.472.camel@pmac.infradead.org>
	<200612131722.17889.paul@codesourcery.com>
	<1166031123.5253.745.camel@pmac.infradead.org>
In-Reply-To: <1166031123.5253.745.camel@pmac.infradead.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200612131742.12393.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Wednesday 13 December 2006 17:32, David Woodhouse wrote:
> 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?

Qemu doesn't currently have any real thread support. It has a few hacks that 
work for simple linuxthreads cases, but I doubt real multithreaded 
applications will work.

My point was that instead of blindly passing the threading syscalls through to 
the host we should consider using the host libc/libpthread thread support.

Paul