From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=35806 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PnILX-0007zY-7b for qemu-devel@nongnu.org; Wed, 09 Feb 2011 17:17:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PnILU-0007fr-9d for qemu-devel@nongnu.org; Wed, 09 Feb 2011 17:17:09 -0500 Received: from moutng.kundenserver.de ([212.227.126.171]:54965) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PnILU-0007fY-27 for qemu-devel@nongnu.org; Wed, 09 Feb 2011 17:17:08 -0500 Message-ID: <4D531235.9040004@mail.berlios.de> Date: Wed, 09 Feb 2011 23:16:21 +0100 From: Stefan Weil MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 2/7] Enable I/O thread and VNC threads by default References: <4D3DFD20.8060004@linux.vnet.ibm.com> <20110125091741.GB30239@edde.se.axis.com> <20110125133453.GC5427@amt.cnet> <20110207101255.GA20413@amt.cnet> <20110207160350.GA26332@amt.cnet> <4D501C71.7090708@redhat.com> <4D50279B.5010102@siemens.com> <4D505DCB.9050406@codemonkey.ws> <20110207214551.GB16429@hall.aurel32.net> <4D50A5F0.802@codemonkey.ws> <20110208072657.GD16429@hall.aurel32.net> <4D50FA14.5010100@redhat.com> <4D5103E8.6050808@siemens.com> <4D510771.3040309@aurel32.net> <4D511221.9030505@siemens.com> <4D5113D3.9090802@aurel32.net> <4D511500.1040303@siemens.com> <4D5115C2.6060008@aurel32.net> <4D51842C.8000209@codemonkey.ws> <4D5125E2.8090902@aurel32.net> <4D5196DE.6030009@codemonkey.ws> <4D514558.9010003@aurel32.net> <4D51AD7D.6060709@codemonkey.ws> <4D515CAB.6040700@aurel32.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: Stefan Hajnoczi , Jan Kiszka , Marcelo Tosatti , "qemu-devel@nongnu.org" , Anthony Liguori , Paul Brook , Paolo Bonzini , "Edgar E. Iglesias" , Aurelien Jarno , Arun Bharadwaj Am 09.02.2011 18:13, schrieb Blue Swirl: > I think win32 situation is somewhat similar (but not nearly as bad as) > to kqemu's. It was useful for some users, but there were no > maintenance and when it got in the way, it was removed because nobody > could fix it. > > But I'd prefer a solution where somebody steps up as Windows > maintainer. I'm also doing regular mingw32 builds but otherwise not > much. > VNC threads can be compiled for W32, too. A short test of the resulting executable was successful, no problems. The patch is available here: http://repo.or.cz/w/qemu/ar7.git/commitdiff/aabf11dc0a938b84d76d7c147cbf0445d7bee297 I decided to create a new directory structure hosts/w32, so files can be moved from the root to hosts/posix, hosts/w32, or hosts/xxx. Include chains reduce code modifications and conditional compilations. And people who don't want to see w32 support can remove it easily :-) Supporting I/O threads for W32 will be possible, too. I don't think that W32 support is a big problem. It never was. Some of the real problems were already named in the previous mails. Regards, Stefan Weil