From: TeLeMan <geleman@gmail.com>
To: quintela@redhat.com
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] vmstate: fix vmstate_subsection_load
Date: Wed, 28 Jul 2010 20:51:02 +0800 [thread overview]
Message-ID: <AANLkTinv+5R4w-pAUxS9cUHPauh76ehyB2qkY8AVFDrY@mail.gmail.com> (raw)
In-Reply-To: <m3zkxbdbwr.fsf@trasno.mitica>
--
SUN OF A BEACH
On Wed, Jul 28, 2010 at 20:32, Juan Quintela <quintela@redhat.com> wrote:
> TeLeMan <geleman@gmail.com> wrote:
>> On Wed, Jul 28, 2010 at 19:51, Juan Quintela <quintela@redhat.com> 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? When I dessigned
> subsections, I looked at all the changes that we had from 0.11 to 0.12,
> subsections can handle all of them. Just curious about what you need.\
>
> Notice that ignoring subsections at this point is not trivial, as
> (sub)sections don't have a size field. Working on getting size there,
> 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.
next prev parent reply other threads:[~2010-07-28 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 4:37 [Qemu-devel] [PATCH] vmstate: fix vmstate_subsection_load TeLeMan
2010-07-28 10:43 ` [Qemu-devel] " Juan Quintela
2010-07-28 11:23 ` TeLeMan
2010-07-28 11:51 ` Juan Quintela
2010-07-28 12:17 ` TeLeMan
2010-07-28 12:32 ` Juan Quintela
2010-07-28 12:51 ` TeLeMan [this message]
2010-07-28 13:12 ` Paolo Bonzini
2010-07-28 13:51 ` 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=AANLkTinv+5R4w-pAUxS9cUHPauh76ehyB2qkY8AVFDrY@mail.gmail.com \
--to=geleman@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).