From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MNqDR-0004K6-T6
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 11:34:49 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MNqDN-0004Hc-8w
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 11:34:49 -0400
Received: from [199.232.76.173] (port=33229 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MNqDM-0004HT-VL
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 11:34:44 -0400
Received: from mx20.gnu.org ([199.232.41.8]:12374)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1MNqDM-0007Bo-BN
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 11:34:44 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1MNqDK-0007qp-HS
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 11:34:42 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] ARM multithreading status
Date: Mon, 6 Jul 2009 16:31:33 +0100
References: <3646AB84-79BE-4327-A732-57661E3C8919@acrodea.co.jp>
In-Reply-To: <3646AB84-79BE-4327-A732-57661E3C8919@acrodea.co.jp>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907061634.39206.paul@codesourcery.com>
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
Cc: Timo Suoranta <timo.suoranta@acrodea.co.jp>

> My problem is that my threading test code manages to create and join
> one pthread, but the next pthread_create, while it starts a new
> thread, doesn't return, and in fact the whole linux system is unable
> to start any new processes until the test program ends.

I assume you're talking about userspace emulation. For system emulation qemu 
doesn't know or care how the guest handles threads, it works just like a real 
machine.

Either way it sounds like a kernel bug. One process should never be able to 
interfere with the rest of the system like this.

Paul