From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCVEY-0008Eh-K0 for qemu-devel@nongnu.org; Mon, 23 Nov 2009 04:29:22 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCVET-0008Dp-Sl for qemu-devel@nongnu.org; Mon, 23 Nov 2009 04:29:22 -0500 Received: from [199.232.76.173] (port=51261 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCVET-0008Dm-MF for qemu-devel@nongnu.org; Mon, 23 Nov 2009 04:29:17 -0500 Received: from mx1.redhat.com ([209.132.183.28]:37721) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NCVET-0008Dw-8S for qemu-devel@nongnu.org; Mon, 23 Nov 2009 04:29:17 -0500 Message-ID: <4B0A55E8.1060105@redhat.com> Date: Mon, 23 Nov 2009 10:29:12 +0100 From: Paolo Bonzini MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: Live migration protocol, device features, ABIs and other beasts References: <4B0952C9.9010803@redhat.com> <4B095D86.700@codemonkey.ws> <4B09F0CA.3060705@codemonkey.ws> <20091123082659.GC2999@redhat.com> In-Reply-To: <20091123082659.GC2999@redhat.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: Gleb Natapov Cc: qemu-devel@nongnu.org On 11/23/2009 09:26 AM, Gleb Natapov wrote: >>> > >I'd go with chunk instead of feature bits, specifying them like in >>> > >the PNG specification: >> > >> > You mean, each device would have multiple sections? We already use >> > chunks for each device state. >> > > Each device can send device info in multiple formats (each format with > its own ID) and destination will choose the one it supports. First of all, we'd need a mechanism to send _lengths_ of chunks. This is especially important since there could be other consumers than QEMU for vm state data, and these may be interested only in few pieces of data. Paolo