From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DcftK-0008I9-JT for qemu-devel@nongnu.org; Mon, 30 May 2005 04:44:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DcftF-0008FH-76 for qemu-devel@nongnu.org; Mon, 30 May 2005 04:44:53 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DcftD-00089O-1H for qemu-devel@nongnu.org; Mon, 30 May 2005 04:44:51 -0400 Received: from [195.129.94.187] (helo=srv94-187.ip-tech.ch) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1DcfpP-00079b-92 for qemu-devel@nongnu.org; Mon, 30 May 2005 04:40:55 -0400 Message-ID: <429AD132.8060803@kberg.ch> Date: Mon, 30 May 2005 10:39:14 +0200 From: Mike Kronenberg MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] cocoa.m References: <429707A8.4040400@kberg.ch> <429733EF.7010308@kberg.ch> <4298BA22.8040101@kberg.ch> <07665104-3687-4286-9B20-55D57C9E8A2E@free.fr> In-Reply-To: <07665104-3687-4286-9B20-55D57C9E8A2E@free.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Pierre d'Herbemont wrote: > > On 28 mai 05, at 20:36, Mike Kronenberg wrote: > >> Pierre d'Herbemont wrote: >> >>> That should be done with not much troubles, if we manage to get >>> qemu thread safe. Did you try that way? >>> >>> >> Until the 7. May I was trying to get all into qemu... sources are >> still there. >> >> I was looking into making the contoller one thread and the each qemu >> a thread, so one can run multiple qemus. It is still on the List - >> but it's a little more time intensive (I use qemu for my work) . So I >> gutted cocoa.m to the elemental UI things... like it is now and made >> a controller with the features I need a lot and I think would be >> useful to have in the final product. >> >> I would like very much, that my patch would be comitted, so bugs can >> be fixed and features added. >> As soon as we can make qemu threadsave, it's easy to merge the >> working frontend with qemu. > > > For now a single-threaded qemu could be ok... The patch will be > smaller, and the multiple instance feature may be added later. What do > you think? I'm looking into it, guess we have to make a qemu class and hide all the static stuff form the controller so we can call qemu as an object and dispose of it at the end, since i did not manage yet to reuse qemu properly for a second time (to many vars and objects to nil). Mike