From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NCVHC-0000d2-FD
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 04:32:06 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NCVH8-0000Zw-38
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 04:32:06 -0500
Received: from [199.232.76.173] (port=51338 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NCVH7-0000Zb-Ax
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 04:32:01 -0500
Received: from mx1.redhat.com ([209.132.183.28]:14670)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gleb@redhat.com>) id 1NCVH6-0000Cd-Iv
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 04:32:00 -0500
Date: Mon, 23 Nov 2009 11:31:57 +0200
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Re: Live migration protocol, device features,
	ABIs and   other beasts
Message-ID: <20091123093157.GD2999@redhat.com>
References: <4B0952C9.9010803@redhat.com> <4B095D86.700@codemonkey.ws>
	<hec6i6$j3r$1@ger.gmane.org> <4B09F0CA.3060705@codemonkey.ws>
	<20091123082659.GC2999@redhat.com> <4B0A55E8.1060105@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B0A55E8.1060105@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org

On Mon, Nov 23, 2009 at 10:29:12AM +0100, Paolo Bonzini wrote:
> 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.
And we need the mechanism to match incoming chunks to a consumer.
Not relay on order of incoming data.

> 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

--
			Gleb.