From: Ashijeet Acharya <ashijeetacharya@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: quintela@redhat.com, armbru@redhat.com,
QEMU Developers <qemu-devel@nongnu.org>,
amit.shah@redhat.com, lcapitulino@redhat.com,
"dgilbert@redhat.com" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Move migrate_set_speed and migrate_set_downtime into migrate_set_parameter
Date: Mon, 5 Sep 2016 13:55:28 +0530 [thread overview]
Message-ID: <CAC2QTZbTL1RAGrHCjd8H_Mp=DVM6w87u647ZsUQeEnuQejQdTw@mail.gmail.com> (raw)
In-Reply-To: <ad5a1cc4-2e4d-0939-c9ca-876e8801677e@redhat.com>
On Mon, Sep 5, 2016 at 1:46 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>
> On 05/09/2016 10:11, Ashijeet Acharya wrote:
>> > > Include migrate_set_speed and migrate_set_downtime inside
>> > > migrate_set_parameters respectively for setting maximum migration
>> > > speed and expected downtime parameters. Also add the query part for
>> > > both in qmp and hmp qemu control interfaces.
>> > >
>> > > Signed-off-by: Ashijeet Acharya <ashijeetacharya@gmail.com>
>> >
>> > You cannot break backwards compatibility for everyone that is using
>> > those commands, sorry.
>>
>> So should I keep the old commands too and add the new ones anyway for
>> the query part?
>
> You do not need query for the old ones, but you can indeed add support
> for speed and downtime in migrate-set-parameters and MigrationParameters.
Right. So I will add the old-commands back and just add support for the new ones
under migration-set-parameters along with the query.
> (Note: I'm not a migration maintainer, so they might say something else).
Okay. I will wait for their views too.
Ashijeet
>
> Paolo
>
>> The old ones will also be modified for query. So we will have
>> compatibility as well as the
>> query.
next prev parent reply other threads:[~2016-09-05 8:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 7:45 [Qemu-devel] [PATCH] Move migrate_set_speed and migrate_set_downtime into migrate_set_parameter Ashijeet Acharya
2016-09-05 8:01 ` Paolo Bonzini
2016-09-05 8:11 ` Ashijeet Acharya
2016-09-05 8:16 ` Paolo Bonzini
2016-09-05 8:25 ` Ashijeet Acharya [this message]
2016-09-05 11:16 ` Dr. David Alan Gilbert
2016-09-05 11:37 ` [Qemu-devel] [PATCH v2] " Ashijeet Acharya
2016-09-05 11:45 ` Paolo Bonzini
2016-09-05 11:59 ` Ashijeet Acharya
2016-09-05 12:01 ` Paolo Bonzini
2016-09-05 12:08 ` Ashijeet Acharya
2016-09-05 13:09 ` Ashijeet Acharya
2016-09-05 13:16 ` Paolo Bonzini
2016-09-05 14:26 ` [Qemu-devel] [PATCH v3] " Ashijeet Acharya
2016-09-05 14:36 ` Daniel P. Berrange
2016-09-05 15:14 ` Ashijeet Acharya
2016-09-05 15:39 ` Daniel P. Berrange
2016-09-05 15:46 ` Ashijeet Acharya
2016-09-05 14:28 ` [Qemu-devel] [PATCH v3] Move migrate_set_speed and migrate_set_downtime into migrate_set_parameter (reversed logic) Ashijeet Acharya
2016-09-05 15:56 ` [Qemu-devel] [PATCH v2] Move migrate_set_speed and migrate_set_downtime into migrate_set_parameter Daniel P. Berrange
2016-09-06 8:16 ` Markus Armbruster
2016-09-06 13:16 ` [Qemu-devel] [PATCH] " 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='CAC2QTZbTL1RAGrHCjd8H_Mp=DVM6w87u647ZsUQeEnuQejQdTw@mail.gmail.com' \
--to=ashijeetacharya@gmail.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@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).