From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:47753) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qh0Nx-0000GW-4e for qemu-devel@nongnu.org; Wed, 13 Jul 2011 10:25:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qh0Nv-00046K-Kb for qemu-devel@nongnu.org; Wed, 13 Jul 2011 10:25:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56509) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qh0Nv-00046E-3F for qemu-devel@nongnu.org; Wed, 13 Jul 2011 10:25:55 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p6DEPs8m025678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 13 Jul 2011 10:25:54 -0400 Message-ID: <4E1DAAEF.9000203@redhat.com> Date: Wed, 13 Jul 2011 16:25:51 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <1310478932-25370-1-git-send-email-alevy@redhat.com> <1310478932-25370-14-git-send-email-alevy@redhat.com> <4E1D44DB.5090803@redhat.com> <20110713092909.GF28430@bow.tlv.redhat.com> <4E1D766C.1090308@redhat.com> <20110713093210.7365d086@doriath> <4E1DA16C.20007@redhat.com> <20110713141008.GN28430@bow.tlv.redhat.com> In-Reply-To: <20110713141008.GN28430@bow.tlv.redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCHv3] qxl-render/qxl: split out qxl_save_ppm List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino , qemu-devel@nongnu.org Hi, >> Hmm. Alon, is it an option to just leave the whole qxl-render stuff >> in sync mode for now and convert it later? Or will that have bad >> interactions with QXL_IO_UPDATE_AREA_ASYNC being used by the guest? >> > It's not a problem. I do have a working version using async monitor command, but > I will gladly put it off if the monitor async is considered harmful. Good, so we know the libspice-server API is sane. Lets put it off for now and resume later when QAPI and the other stuff is sorted, async i/o commands and s3/s4 support are more important now. cheers, Gerd