From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LLMd5-0004bC-E2 for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:02:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LLMd4-0004av-Ui for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:02:47 -0500 Received: from [199.232.76.173] (port=46605 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LLMd4-0004as-Qr for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:02:46 -0500 Received: from mail-ew0-f21.google.com ([209.85.219.21]:45512) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LLMd4-0007vF-A4 for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:02:46 -0500 Received: by ewy14 with SMTP id 14so10968516ewy.10 for ; Fri, 09 Jan 2009 11:02:45 -0800 (PST) Message-ID: <49679F4C.1070603@codemonkey.ws> Date: Fri, 09 Jan 2009 13:02:36 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Ongoing changes to the displaying code References: <4966ADD4.5090102@codesourcery.com> <4966BB7A.3090303@codemonkey.ws> <4966BEC4.7080903@codemonkey.ws> <60cad3f0901090128m23977527kf658c15ba90dbaf8@mail.gmail.com> <49676B43.2020406@codemonkey.ws> <18791.34404.878201.724561@mariner.uk.xensource.com> <60cad3f0901090926x1595e64cw1d646b91c40a1e42@mail.gmail.com> In-Reply-To: <60cad3f0901090926x1595e64cw1d646b91c40a1e42@mail.gmail.com> 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 David Turner wrote: > > > On Fri, Jan 9, 2009 at 6:16 PM, Ian Jackson > wrote: > > I think it's fair enough for people to prefer SDL to VNC for a number > of reasons. But why not just allow them to embed the qemu SDL window > in their application ? This is definitely possible in X although I'm > not sure exactly how to do it with SDL. > > > to be fair, that might not be an ideal solution. QEMU emulation > currently requires frequent SIGALRM signals. > this means the application will not be able to use it for its own > needs, and a *lot* of system calls are going to > randomly return EINTR, which a *lot* of code doesn't handle properly > (*cough* *cough* libesd.so) > Not to mention the fact that if you block too long or have long running computations, you'll cause great amounts of pain to the guest. You also can't use main loops which makes gui integration pretty difficult. It's really a bad environment for GUIs. I understand the lack of desire to rewrite working code, but external GUIs are really the best technical solution for QEMU. Regards, Anthony Liguori > > Ian. > > >