From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MLDU6-00088G-Uo for qemu-devel@nongnu.org; Mon, 29 Jun 2009 05:49:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MLDU1-000872-As for qemu-devel@nongnu.org; Mon, 29 Jun 2009 05:49:09 -0400 Received: from [199.232.76.173] (port=39256 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MLDU1-00086z-47 for qemu-devel@nongnu.org; Mon, 29 Jun 2009 05:49:05 -0400 Received: from mx2.redhat.com ([66.187.237.31]:48259) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MLDU0-0006mW-L6 for qemu-devel@nongnu.org; Mon, 29 Jun 2009 05:49:04 -0400 Message-ID: <4A488E65.2000605@redhat.com> Date: Mon, 29 Jun 2009 12:50:29 +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> <4A476D46.2000909@redhat.com> <4A47A8AF.3030905@codemonkey.ws> In-Reply-To: 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: Stefano Stabellini Cc: "ehabkost@redhat.com" , "jan.kiszka@siemens.com" , "dlaor@redhat.com" , "qemu-devel@nongnu.org" , Luiz Capitulino , Filip Navara , Vincent Hanquez On 06/29/2009 12:44 PM, Stefano Stabellini wrote: > I think it would be a good idea to allow binary as > Content-Transfer-Encoding, since base64 is very inefficient for > transferring large amount of data. > For example we may want to save the state of the guest, including the > whole memory, and transfer it over the network without saving it to file > first. > The migrate command does that. Give it an fd and migrate away. Mixing binary in the data format seems a bad idea to me, especially if we stick to json as our encoding. -- error compiling committee.c: too many arguments to function