From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCUGN-00011X-5Z for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:27:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCUGH-0000w2-3N for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:27:10 -0500 Received: from [199.232.76.173] (port=33943 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCUGG-0000vo-JG for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:27:04 -0500 Received: from mx20.gnu.org ([199.232.41.8]:50126) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NCUGF-0006y7-PR for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:27:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NCUGE-0006cm-Mu for qemu-devel@nongnu.org; Mon, 23 Nov 2009 03:27:03 -0500 Date: Mon, 23 Nov 2009 10:26:59 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] Re: Live migration protocol, device features, ABIs and other beasts Message-ID: <20091123082659.GC2999@redhat.com> References: <4B0952C9.9010803@redhat.com> <4B095D86.700@codemonkey.ws> <4B09F0CA.3060705@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B09F0CA.3060705@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Paolo Bonzini , qemu-devel@nongnu.org On Sun, Nov 22, 2009 at 08:17:46PM -0600, Anthony Liguori wrote: > Paolo Bonzini wrote: > > > >>I don't see how this fixes anything. If you used feature bits, how do > >>you migrate from a version that has a feature bit that an older version > >>doesn't know about? Do you just ignore it? > > > >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. -- Gleb.