From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, lcapitulino@redhat.com, qemu-devel@nongnu.org,
laine@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/7] runstate: Add runstate store
Date: Wed, 22 Oct 2014 12:18:52 +0100 [thread overview]
Message-ID: <20141022111851.GD2296@work-vm> (raw)
In-Reply-To: <544527BB.1060500@redhat.com>
* Eric Blake (eblake@redhat.com) wrote:
> On 10/20/2014 04:52 AM, Juan Quintela wrote:
> > "Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
> >> * Juan Quintela (quintela@redhat.com) wrote:
> >>> This allows us to store the current state to send it through migration.
> >>
> >> Why store the runstate as a string? The later code then ends up doing
> >> string compares and things - why not just use the enum value?
> >
> > How do you know that it has the same values both sides? As far as I can
> > see, all interaction with the outside is done with strings (i.e. QMP).
>
> If it's part of the migration stream, then it is not something visible
> in QMP, and it is your own fault if you ever change the enum values in
> such a way that the migration stream is incompatible between versions.
> I think using an enum in the migration stream is just fine, and more
> efficient.
I think the question here really comes from RunState being an enum defined
in qapi-schema.json; so we could use that directly in the migration stream
if we were guaranteed that the encoding of that enum wasn't going to change.
Does qapi make any guarantees about the enum encoding?
Dave
>
> >
> > But it is easier for me if I can sent the numeric value.
> >
> > Libvirt folks?
>
> As far as I can tell, libvirt is unimpacted by HOW it is represented in
> the migration stream, only that the destination is able to inform
> libvirt what state was received as part of migration, with libvirt
> having an easy way to then get back into that state (of course, libvirt
> should also still have the option to choose a different state than what
> just got migrated, as in the case where the user pauses the source in
> order to avoid convergence problems but wants the destination to start
> running again).
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2014-10-22 11:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 7:55 [Qemu-devel] [RFC 0/7] Optional toplevel sections Juan Quintela
2014-10-15 7:55 ` [Qemu-devel] [PATCH 1/7] migration: Create optional sections Juan Quintela
2014-10-15 7:55 ` [Qemu-devel] [PATCH 2/7] runstate: Add runstate store Juan Quintela
2014-10-20 10:24 ` Dr. David Alan Gilbert
2014-10-20 10:52 ` Juan Quintela
2014-10-20 15:18 ` Eric Blake
2014-10-22 11:18 ` Dr. David Alan Gilbert [this message]
2014-10-22 11:40 ` Markus Armbruster
2014-10-22 15:52 ` Eric Blake
2014-10-15 7:55 ` [Qemu-devel] [PATCH 3/7] runstate: create runstate_index function Juan Quintela
2014-10-15 7:55 ` [Qemu-devel] [PATCH 4/7] runstate: migration allows more transitions now Juan Quintela
2014-10-15 14:42 ` Eric Blake
2014-10-15 15:50 ` Juan Quintela
2014-11-03 12:46 ` Amit Shah
2014-10-15 7:55 ` [Qemu-devel] [PATCH 5/7] migration: create now section to store global state Juan Quintela
2014-10-20 10:52 ` Dr. David Alan Gilbert
2014-10-20 11:11 ` Kevin Wolf
2014-10-15 7:55 ` [Qemu-devel] [PATCH 6/7] global_state: Make section optional Juan Quintela
2014-10-15 7:55 ` [Qemu-devel] [PATCH 7/7] vmstate: Create optional sections Juan Quintela
2014-10-15 14:45 ` Eric Blake
2014-10-15 14:57 ` [Qemu-devel] [RFC 0/7] Optional toplevel sections Eric Blake
2014-10-15 15:59 ` Juan Quintela
2014-10-15 16:37 ` Eric Blake
2014-10-17 13:41 ` Paolo Bonzini
2014-10-20 14:59 ` Dr. David Alan Gilbert
2014-10-20 11:29 ` Kevin Wolf
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=20141022111851.GD2296@work-vm \
--to=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=laine@redhat.com \
--cc=lcapitulino@redhat.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).