From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33534 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OsHMH-0007Q0-C6 for qemu-devel@nongnu.org; Sun, 05 Sep 2010 11:42:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OsHLt-0007Kc-Gi for qemu-devel@nongnu.org; Sun, 05 Sep 2010 11:42:17 -0400 Received: from mail-fx0-f45.google.com ([209.85.161.45]:33909) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OsHLt-0007KU-Aq for qemu-devel@nongnu.org; Sun, 05 Sep 2010 11:41:53 -0400 Received: by fxm7 with SMTP id 7so2358167fxm.4 for ; Sun, 05 Sep 2010 08:41:52 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <4C83BA3C.7060402@redhat.com> Date: Sun, 05 Sep 2010 17:41:48 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <4C62825A.6000903@mail.berlios.de> <4C685F5D.2090707@codemonkey.ws> <4C69A29F.5000606@codemonkey.ws> <4C6AE96C.2040907@codemonkey.ws> <4C6B9A73.90903@redhat.com> <3BD70645-0CD6-48BC-90DE-EF1E43AD0DCF@web.de> In-Reply-To: <3BD70645-0CD6-48BC-90DE-EF1E43AD0DCF@web.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: [Qemu-devel] Re: Unmaintained QEMU builds List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-1?Q?Andreas_F=E4rber?= Cc: Blue Swirl , QEMU Developers On 09/04/2010 04:03 PM, Andreas Färber wrote: > For BeOS there once was a pthreads library project. Maybe the same could > work for Win32, implement the pthreads API and map to corresponding > Win32 API functions? Then QEMU could use pthreads API and use wrappers > only where strictly necessary. In theory this sounds less invasive. There's pthread-win32 but it requires a kernel module to support signals; alternatively, with some care (if you call the Win32 API yourself, you have to ensure signals are never delivered during API calls) Cygwin provides the pthreads API as well. But both are quite heavy-weight, and implementing the subset everybody really cares about (thread creation/joining, mutexes, condition variables, plus QEMU needs one inter-thread signal) is really easy. The main thing is what you wrote in another message: what can QEMU offer on Windows and Darwin that semi-free Virtual Box and proprietary VMware cannot? I like to think that it can offer something, but maybe I'm wrong. :/ Paolo