From: Juan Quintela <quintela@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: The State of the SaveVM format
Date: Thu, 10 Sep 2009 14:55:07 +0200 [thread overview]
Message-ID: <m3fxavklhw.fsf@neno.mitica> (raw)
In-Reply-To: <20090910120802.GA24530@redhat.com> (Michael S. Tsirkin's message of "Thu, 10 Sep 2009 15:08:03 +0300")
"Michael S. Tsirkin" <mst@redhat.com> 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.
next prev parent reply other threads:[~2009-09-10 12:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 8:47 [Qemu-devel] The State of the SaveVM format Juan Quintela
2009-09-09 8:54 ` [Qemu-devel] " Michael S. Tsirkin
2009-09-09 9:22 ` Juan Quintela
2009-09-09 9:33 ` Michael S. Tsirkin
2009-09-09 9:01 ` Michael S. Tsirkin
2009-09-09 9:26 ` Juan Quintela
2009-09-09 12:00 ` Michael S. Tsirkin
2009-09-09 14:33 ` [Qemu-devel] " Gerd Hoffmann
2009-09-09 14:41 ` Anthony Liguori
2009-09-09 14:49 ` [Qemu-devel] " Juan Quintela
2009-09-09 14:57 ` Anthony Liguori
2009-09-09 15:22 ` [Qemu-devel] " Gerd Hoffmann
2009-09-09 15:46 ` Anthony Liguori
2009-09-09 15:47 ` Anthony Liguori
2009-09-10 1:10 ` Markus Armbruster
2009-09-10 1:26 ` Markus Armbruster
2009-09-10 2:02 ` Anthony Liguori
2009-09-10 12:08 ` Michael S. Tsirkin
2009-09-10 12:55 ` Juan Quintela [this message]
2009-09-10 13:07 ` [Qemu-devel] " Michael S. Tsirkin
2009-09-10 13:26 ` Juan Quintela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3fxavklhw.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.