All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: TeLeMan <geleman@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] vmstate: fix vmstate_subsection_load
Date: Wed, 28 Jul 2010 14:32:52 +0200	[thread overview]
Message-ID: <m3zkxbdbwr.fsf@trasno.mitica> (raw)
In-Reply-To: <AANLkTik8Z2cRsqSUqK0zBPYSL=yF6xUS2mE23JVEoC4S@mail.gmail.com> (TeLeMan's message of "Wed, 28 Jul 2010 20:17:27 +0800")

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).

Later, Juan.

  reply	other threads:[~2010-07-28 12:34 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 [this message]
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=m3zkxbdbwr.fsf@trasno.mitica \
    --to=quintela@redhat.com \
    --cc=geleman@gmail.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.