All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Glauber Costa <glommer@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] augment info migrate with page status
Date: Thu, 21 May 2009 13:55:26 -0500	[thread overview]
Message-ID: <4A15A39E.4030800@us.ibm.com> (raw)
In-Reply-To: <1242930415-20085-1-git-send-email-glommer@redhat.com>

Glauber Costa wrote:
> This patch augments info migrate output with status about:
> * ram bytes remaining
> * ram bytes transferred
> * ram bytes total
>
> This should be enough for management tools to realize
> whether or not there is progress in migration. We can
> add more information later on, if the need arrives
>
> Signed-off-by: Glauber Costa <glommer@redhat.com>
> ---
>  migration.c |    3 +++
>  sysemu.h    |    4 ++++
>  vl.c        |   21 ++++++++++++++++++++-
>  3 files changed, 27 insertions(+), 1 deletions(-)
>
> diff --git a/migration.c b/migration.c
> index b9e3368..a771f37 100644
> --- a/migration.c
> +++ b/migration.c
> @@ -116,6 +116,9 @@ void do_info_migrate(Monitor *mon)
>          switch (s->get_status(s)) {
>          case MIG_STATE_ACTIVE:
>              monitor_printf(mon, "active\n");
> +            monitor_printf(mon, "transferred ram: %lu kbytes\n", ram_bytes_transferred() >> 10);
> +            monitor_printf(mon, "remaining ram: %lu kbytes\n", ram_bytes_remaining() >> 10);
> +            monitor_printf(mon, "total ram: %lu kbytes\n", ram_bytes_total() >> 10);
>   

ram_addr_t isn't %lu.  It's 64-bit.  There's a PRI macro somewhere for it...

-- 
Regards,

Anthony Liguori

  reply	other threads:[~2009-05-21 18:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 18:26 [Qemu-devel] [PATCH] augment info migrate with page status Glauber Costa
2009-05-21 18:55 ` Anthony Liguori [this message]
2009-05-24  8:35   ` [Qemu-devel] " Avi Kivity

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=4A15A39E.4030800@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=glommer@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.