From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MljBJ-00019M-Fd for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:55:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MljBE-000191-R3 for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:55:21 -0400 Received: from [199.232.76.173] (port=60331 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MljBE-00018w-ML for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:55:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58680) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MljBE-0004BU-4F for qemu-devel@nongnu.org; Thu, 10 Sep 2009 08:55:16 -0400 From: Juan Quintela In-Reply-To: <20090910120802.GA24530@redhat.com> (Michael S. Tsirkin's message of "Thu, 10 Sep 2009 15:08:03 +0300") References: <4AA7BEA7.6080906@codemonkey.ws> <87my53lhd1.fsf@pike.pond.sub.org> <4AA85E1F.6000902@codemonkey.ws> <20090910120802.GA24530@redhat.com> Date: Thu, 10 Sep 2009 14:55:07 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Qemu-devel] Re: The State of the SaveVM format List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Markus Armbruster , qemu-devel@nongnu.org "Michael S. Tsirkin" wrote: > On Wed, Sep 09, 2009 at 09:02:07PM -0500, Anthony Liguori wrote: >>> If we complicate vmstate now to shoehorn pre-vmstate >>> formats into vmstate, that ancient history will continue to haunt us. >>> Complicating a program is far easier than the other direction. >>> >> >> Let's take it one step at a time. There is an awful lot of areas where >> we can support older versions without adding complications. Let's >> approach the complicated ones one at a time. > > I'm not sure I understand this talk about "pre-vmstate formats". > I thought vmstate patches were, at least for the most part, trying > to reimplement existing format with the table-driver design? > > If that's not so and we are changing the format now, is it too late to > consider some standard serialization format rather than rolling our own? We are using previous format. At some point we should move to other format. When/what is still not decided. Each time at its time. Once we have everything using vmstate, we have a declarative description of the state. Going for tables with names + types to any format is just an exercise of walking the tables and writing a pretty-printer and a parser. Later, Juan.