From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] block-migration: deprecate block migration for the 1.2 release
Date: Tue, 14 Aug 2012 15:48:37 +0200 [thread overview]
Message-ID: <502A5735.1010409@redhat.com> (raw)
In-Reply-To: <1344951151-26387-1-git-send-email-aliguori@us.ibm.com>
Am 14.08.2012 15:32, schrieb Anthony Liguori:
> To be replaced with live block copy.
>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Might be worth adding a deprecation note in qapi-schema.json.
> ---
> migration.c | 9 +++++++++
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/migration.c b/migration.c
> index 653a3c1..babccf4 100644
> --- a/migration.c
> +++ b/migration.c
> @@ -482,10 +482,19 @@ void qmp_migrate(const char *uri, bool has_blk, bool blk,
> MigrationParams params;
> const char *p;
> int ret;
> + static bool suppress_deprecation_message;
>
> params.blk = blk;
> params.shared = inc;
>
> + if (blk && !suppress_deprecation_message) {
Hm, it's consistent with when we start block migration, but has_blk is
completely ignored for that and blk seems to be uninitialised if
!has_blk. I think this needs to be fixed. (Why does qmp-marshal.c even
compile when it can use blk uninitialised...?)
Kevin
> + qerror_report(ERROR_CLASS_GENERIC_ERROR,
> + "Block migration is deprecated. "
> + "See http://wiki.qemu.org/Features/LiveBlockCopy "
> + "for an alternative syntax.");
> + suppress_deprecation_message = true;
> + }
> +
> if (s->state == MIG_STATE_ACTIVE) {
> error_set(errp, QERR_MIGRATION_ACTIVE);
> return;
>
next prev parent reply other threads:[~2012-08-14 13:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 13:32 [Qemu-devel] [PATCH] block-migration: deprecate block migration for the 1.2 release Anthony Liguori
2012-08-14 13:48 ` Kevin Wolf [this message]
2012-08-14 14:52 ` Luiz Capitulino
2012-08-14 15:02 ` Kevin Wolf
2012-08-14 15:48 ` Luiz Capitulino
2012-08-14 15:59 ` Kevin Wolf
2012-08-14 14:42 ` Stefan Hajnoczi
2012-08-15 8:12 ` Ruben Kerkhof
2012-08-15 12:38 ` Stefan Hajnoczi
2012-08-16 7:37 ` Ruben Kerkhof
2012-08-18 19:08 ` Paolo Bonzini
2012-08-19 8:13 ` Ruben Kerkhof
2012-08-20 8:23 ` Paolo Bonzini
2012-08-20 8:47 ` Ruben Kerkhof
2012-08-18 19:10 ` Paolo Bonzini
2012-08-14 14:49 ` Luiz Capitulino
2012-08-14 19:45 ` Anthony Liguori
2012-08-14 20:25 ` Markus Armbruster
2012-08-14 20:32 ` Luiz Capitulino
2012-08-14 20:26 ` Luiz Capitulino
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=502A5735.1010409@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).