qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Orit Wasserman <owasserm@redhat.com>
Cc: armbru@redhat.com, mrhines@us.ibm.com, qemu-devel@nongnu.org,
	quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] Fix query-migrate documentation in qmp-commands.hx
Date: Mon, 19 Aug 2013 14:41:30 -0400	[thread overview]
Message-ID: <20130819144130.1569e7a6@redhat.com> (raw)
In-Reply-To: <20130812101952.2f065724@redhat.com>

On Mon, 12 Aug 2013 10:19:52 -0400
Luiz Capitulino <lcapitulino@redhat.com> wrote:

> On Thu,  8 Aug 2013 20:05:48 +0300
> Orit Wasserman <owasserm@redhat.com> wrote:
> 
> > "ram" is present also when migration completes.
> > expected-downtime, total-time and downtime are no longer part of "ram" data.
> > 
> > Signed-off-by: Orit Wasserman <owasserm@redhat.com>
> 
> Applied to the qmp branch, thanks.

This one missed the deadline for 1.6. I'm my updating my tree for 1.7,
but this patch conflicts with 8f3067, which repeated for the setup-time
key the mistake this patch is fixing for other keys.

We need a respin for this patch, which should also move setup-time
to the main dict. Orit, I can do it myself if you want.

> 
> > ---
> >  qmp-commands.hx | 20 ++++++++++----------
> >  1 file changed, 10 insertions(+), 10 deletions(-)
> > 
> > diff --git a/qmp-commands.hx b/qmp-commands.hx
> > index 2e59b0d..a22a841 100644
> > --- a/qmp-commands.hx
> > +++ b/qmp-commands.hx
> > @@ -2626,8 +2626,8 @@ The main json-object contains the following:
> >  - "expected-downtime": only present while migration is active
> >                  total amount in ms for downtime that was calculated on
> >                  the last bitmap round (json-int)
> > -- "ram": only present if "status" is "active", it is a json-object with the
> > -  following RAM information:
> > +- "ram": only present if "status" is "active" or "complete", it is a
> > +         json-object with the following RAM information:
> >           - "transferred": amount transferred in bytes (json-int)
> >           - "remaining": amount remaining to transfer in bytes (json-int)
> >           - "total": total amount of memory in bytes (json-int)
> > @@ -2669,12 +2669,12 @@ Examples:
> >  -> { "execute": "query-migrate" }
> >  <- { "return": {
> >          "status": "completed",
> > +        "total-time":12345,
> > +        "downtime":12345,
> >          "ram":{
> >            "transferred":123,
> >            "remaining":123,
> >            "total":246,
> > -          "total-time":12345,
> > -          "downtime":12345,
> >            "duplicate":123,
> >            "normal":123,
> >            "normal-bytes":123456
> > @@ -2693,12 +2693,12 @@ Examples:
> >  <- {
> >        "return":{
> >           "status":"active",
> > +         "total-time":12345,
> > +         "expected-downtime":12345,
> >           "ram":{
> >              "transferred":123,
> >              "remaining":123,
> >              "total":246,
> > -            "total-time":12345,
> > -            "expected-downtime":12345,
> >              "duplicate":123,
> >              "normal":123,
> >              "normal-bytes":123456
> > @@ -2712,12 +2712,12 @@ Examples:
> >  <- {
> >        "return":{
> >           "status":"active",
> > +         "total-time":12345,
> > +         "expected-downtime":12345,
> >           "ram":{
> >              "total":1057024,
> >              "remaining":1053304,
> >              "transferred":3720,
> > -            "total-time":12345,
> > -            "expected-downtime":12345,
> >              "duplicate":123,
> >              "normal":123,
> >              "normal-bytes":123456
> > @@ -2736,13 +2736,13 @@ Examples:
> >  <- {
> >        "return":{
> >           "status":"active",
> > +         "total-time":12345,
> > +         "expected-downtime":12345,
> >           "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
> >           "ram":{
> >              "total":1057024,
> >              "remaining":1053304,
> >              "transferred":3720,
> > -            "total-time":12345,
> > -            "expected-downtime":12345,
> >              "duplicate":10,
> >              "normal":3333,
> >              "normal-bytes":3412992
> 

  reply	other threads:[~2013-08-19 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08 17:05 [Qemu-devel] [PATCH v2] Fix query-migrate documentation in qmp-commands.hx Orit Wasserman
2013-08-08 18:41 ` Eric Blake
2013-08-08 21:31   ` Michael R. Hines
2013-08-12 14:19 ` Luiz Capitulino
2013-08-19 18:41   ` Luiz Capitulino [this message]
2013-08-20 10:33     ` Orit Wasserman

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=20130819144130.1569e7a6@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mrhines@us.ibm.com \
    --cc=owasserm@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).