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 19:23:50 +0800 [thread overview]
Message-ID: <AANLkTikay3_JE7AO9AzE06umGjREd2ArCTZRkPBsgudd@mail.gmail.com> (raw)
In-Reply-To: <m38w4vga4h.fsf@trasno.mitica>
On Wed, Jul 28, 2010 at 18:43, Juan Quintela <quintela@redhat.com> wrote:
> TeLeMan <geleman@gmail.com> wrote:
>> If the new version adds the new subsection for some vmstate, the old
>> version will load the new version's vmstate unsuccessfully. So we have
>> to ignore the unrecognized subsections.
>
> No. That was the whole point of subsections. If one subsection is
> sent, target machine has to understand it. If it don't understand it,
> it fails.
>
> If subsection is not needed, it is the responsability of the source to
> not send it.
>
> This was one of the design requirements. Subsections are optional but
> it is the source which decides which ones to send/not to send. The
> target has to understand everything that it gets or fail the migration.
>
If the target must understand everything, the vmstate's version will
be useless because the old version target maybe cannot load the new
version target's vmstate.
next prev parent reply other threads:[~2010-07-28 11:23 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 [this message]
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
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=AANLkTikay3_JE7AO9AzE06umGjREd2ArCTZRkPBsgudd@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).