From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MKuEM-0001Z5-GL for qemu-devel@nongnu.org; Sun, 28 Jun 2009 09:15:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MKuEH-0001Xq-Os for qemu-devel@nongnu.org; Sun, 28 Jun 2009 09:15:37 -0400 Received: from [199.232.76.173] (port=33853 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MKuEH-0001Xj-Lo for qemu-devel@nongnu.org; Sun, 28 Jun 2009 09:15:33 -0400 Received: from mx2.redhat.com ([66.187.237.31]:55301) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MKuEH-0006E5-7G for qemu-devel@nongnu.org; Sun, 28 Jun 2009 09:15:33 -0400 Message-ID: <4A476D46.2000909@redhat.com> Date: Sun, 28 Jun 2009 16:16:54 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file References: <4A412339.5000109@redhat.com> <4A4395B8.4010401@redhat.com> <4A43BD5D.80307@codemonkey.ws> <4A43C264.6060803@redhat.com> <4A43D600.8060605@codemonkey.ws> <4A449113.8070907@redhat.com> <4A44CB74.1070808@codemonkey.ws> <4A44E2F3.8050804@codemonkey.ws> <5b31733c0906261036o272bcd8xffc0f2e209b778a5@mail.gmail.com> <4A45232F.50306@codemonkey.ws> <5b31733c0906261325ye5fe937wea277c2d87ccd1e1@mail.gmail.com> In-Reply-To: <5b31733c0906261325ye5fe937wea277c2d87ccd1e1@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Filip Navara Cc: "ehabkost@redhat.com" , Stefano Stabellini , "jan.kiszka@siemens.com" , "dlaor@redhat.com" , "qemu-devel@nongnu.org" , Luiz Capitulino , Vincent Hanquez On 06/26/2009 11:25 PM, Filip Navara wrote: >> I don't think binary data is a requirement. An FDT should be transmitted as >> a tree, not as a binary blob. You could also transmit binary as a list of >> bytes though. >> > > You can transmit it as list of bytes and it's woefully inefficient. I > gave the FDT as an example, but I believe that binary data may be > needed in future for one purpose or another. The monitor already > provides a way to dump guest memory and I see no reason to not > transfer it using some "binary" encoding. > Another candidate is screendump. There's no reason to go through a file. We could pass a pipe as an fd and request a screendump to that fd, but that's rather roundabout. -- error compiling committee.c: too many arguments to function