From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props
Date: Wed, 12 Jul 2017 20:02:40 +0100 [thread overview]
Message-ID: <20170712190240.GM30658@work-vm> (raw)
In-Reply-To: <1499842423-21101-1-git-send-email-peterx@redhat.com>
* Peter Xu (peterx@redhat.com) wrote:
> We have the MigrationState as QDev now (which seems crazy). Let's
> continue to benefit.
>
> This series is exporting all migration capabilities/params as global
> parameters. Then we can do something like this:
>
> qemu -global migration.postcopy-ram=true \
> -global migration.max-bandwidth=4096
>
> The values will be inited just like we typed these values into HMP
> monitor. It'll simplify lots of migration scripts.
>
> The changes are fairly straightforward. One tiny loss is that we still
> don't support:
>
> -global migration.max-bandwidth=1g
>
> ...just like what we did in HMP:
>
> migrate_set_speed 1g
>
> ...while we need to use:
>
> -global migration.max-bandwidth=1073741824
>
> However that should only be used in scripts, and that's good enough
> imho.
>
> These properties should only be used for debugging/testing purpose,
> and we should not guarantee any interface compatibility for them (just
> like HMP).
I guess the sanity checks in qmp_migrate_set_parameters and
qmp_migrate_set_capabilities aren't run?
Also, have you done any checks on multiple migrations; e.g. it's good
to check that the flags/state are all preserved if we do a migrate, that
migrate fails or is cancelled and then you do a 2nd migrate.
Dave
> Please review. Thanks.
>
> Peter Xu (3):
> qdev: provide DEFINE_PROP_INT64()
> migration: export parameters to props
> migration: export capabilities to props
>
> hw/core/qdev-properties.c | 32 +++++++++++++++++++++++++++
> include/hw/qdev-properties.h | 3 +++
> migration/migration.c | 52 +++++++++++++++++++++++++++++++++++---------
> 3 files changed, 77 insertions(+), 10 deletions(-)
>
> --
> 2.7.4
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-07-12 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 6:53 [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props Peter Xu
2017-07-12 6:53 ` [Qemu-devel] [PATCH 1/3] qdev: provide DEFINE_PROP_INT64() Peter Xu
2017-07-13 16:05 ` Marc-André Lureau
2017-07-14 3:06 ` Peter Xu
2017-07-12 6:53 ` [Qemu-devel] [PATCH 2/3] migration: export parameters to props Peter Xu
2017-07-12 18:49 ` Dr. David Alan Gilbert
2017-07-12 6:53 ` [Qemu-devel] [PATCH 3/3] migration: export capabilities " Peter Xu
2017-07-12 18:59 ` Dr. David Alan Gilbert
2017-07-12 19:02 ` Dr. David Alan Gilbert [this message]
2017-07-14 4:23 ` [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props Peter Xu
2017-07-14 15:57 ` Eduardo Habkost
2017-07-17 3:25 ` Peter Xu
2017-07-12 19:05 ` Eduardo Habkost
2017-07-14 5:04 ` Peter Xu
2017-07-14 16:01 ` Eduardo Habkost
2017-07-14 16:32 ` Dr. David Alan Gilbert
2017-07-17 3:06 ` Peter Xu
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=20170712190240.GM30658@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@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).