qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ashijeet Acharya <ashijeetacharya@gmail.com>
To: quintela@redhat.com
Cc: lcapitulino@redhat.com, amit.shah@redhat.com, eblake@redhat.com,
	armbru@redhat.com, "dgilbert@redhat.com" <dgilbert@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] Move max-bandwidth and downtime-limit into migrate_set_parameter for both hmp and qmp
Date: Wed, 7 Sep 2016 18:22:20 +0530	[thread overview]
Message-ID: <CAC2QTZaV2A8w6EmWU64abCeEUONMg=+h9kUnLA2UxJDjEcRMUQ@mail.gmail.com> (raw)
In-Reply-To: <87wpio9k5e.fsf@emacs.mitica>

On Wed, Sep 7, 2016 at 2:11 PM, Juan Quintela <quintela@redhat.com> wrote:
> Ashijeet Acharya <ashijeetacharya@gmail.com> wrote:
>> Mark old-commands for speed and downtime as deprecated.
>> Move max-bandwidth and downtime-limit into migrate-set-parameters for
>> setting maximum migration speed and expected downtime limit parameters
>> respectively.
>> Change downtime units to milliseconds (only for new-command) and update
>> the query part in both hmp and qmp qemu control interfaces.
>>
>> Signed-off-by: Ashijeet Acharya <ashijeetacharya@gmail.com>
>
>
> Thanks, applied for 2.8.

Great! Thanks a lot.

Ashijeet
>
> Later, Juan.

  reply	other threads:[~2016-09-07 12:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 13:39 [Qemu-devel] [PATCH v3] Move max-bandwidth and downtime-limit into migrate_set_parameter for both hmp and qmp Ashijeet Acharya
2016-09-07  8:41 ` Juan Quintela
2016-09-07 12:52   ` Ashijeet Acharya [this message]
2016-09-07 22:03 ` Eric Blake
2016-09-08  7:55   ` Ashijeet Acharya
2016-09-08 14:41   ` Juan Quintela
2016-09-08 15:30     ` Ashijeet Acharya
2016-09-08 15:39       ` Eric Blake

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='CAC2QTZaV2A8w6EmWU64abCeEUONMg=+h9kUnLA2UxJDjEcRMUQ@mail.gmail.com' \
    --to=ashijeetacharya@gmail.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@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).