From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=47862 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oe66C-0000LD-MZ for qemu-devel@nongnu.org; Wed, 28 Jul 2010 08:51:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oe66B-0008E4-Lx for qemu-devel@nongnu.org; Wed, 28 Jul 2010 08:51:04 -0400 Received: from mail-vw0-f45.google.com ([209.85.212.45]:38595) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oe66B-0008Dz-Jl for qemu-devel@nongnu.org; Wed, 28 Jul 2010 08:51:03 -0400 Received: by vws19 with SMTP id 19so4331313vws.4 for ; Wed, 28 Jul 2010 05:51:03 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 28 Jul 2010 20:51:02 +0800 Message-ID: From: TeLeMan Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Re: [PATCH] vmstate: fix vmstate_subsection_load List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: quintela@redhat.com Cc: qemu-devel -- SUN OF A BEACH On Wed, Jul 28, 2010 at 20:32, Juan Quintela wrote: > TeLeMan wrote: >> On Wed, Jul 28, 2010 at 19:51, Juan Quintela wrote= : >>> I hope this hepls to understand how subsections are supposed to work. >>> >>> Thanks for the comments, Juan. >>> >> I see, thanks a lot. But I still hope to have the similar subsection >> that can be ignored simply. > > Then it is better not to be sent in the 1st place. > > Do you have any example of why you want to do? =C2=A0When I dessigned > subsections, I looked at all the changes that we had from 0.11 to 0.12, > subsections can handle all of them. =C2=A0Just curious about what you nee= d.\ > > Notice that ignoring subsections at this point is not trivial, as > (sub)sections don't have a size field. =C2=A0Working on getting size ther= e, > but it is a long term project (it requires 1st to change everything to > VMState to be able to change how QEMUFile works). I have some extra data to be saved to vmstate and I want the new vmstate to be compatible with the official version. You are right, I thought it was simple. Now I discard my thought.