All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com, aarcange@redhat.com,
	den@openvz.org, marcel.a@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 2/6] Migration: Split out ram part of qmp_query_migrate
Date: Mon, 23 May 2016 12:32:08 +0530	[thread overview]
Message-ID: <20160523070208.GA24417@grmbl.mre> (raw)
In-Reply-To: <1463489755-30703-3-git-send-email-dgilbert@redhat.com>

On (Tue) 17 May 2016 [13:55:51], Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> The RAM section of qmp_query_migrate is reasonably complex
> and repeated 3 times.  Split it out into a helper.
> 
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Reviwed-by: Denis V. Lunev <den@openvz.org>
> ---
>  migration/migration.c | 57 ++++++++++++++++++++-------------------------------
>  1 file changed, 22 insertions(+), 35 deletions(-)
> 
> diff --git a/migration/migration.c b/migration/migration.c
> index 991313a..bfb326d 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -561,6 +561,25 @@ static void get_xbzrle_cache_stats(MigrationInfo *info)
>      }
>  }
>  
> +static void populate_ram_info(MigrationInfo *info, MigrationState *s)
> +{
> +    info->has_ram = true;
> +    info->ram = g_malloc0(sizeof(*info->ram));
> +    info->ram->transferred = ram_bytes_transferred();
> +    info->ram->total = ram_bytes_total();
> +    info->ram->duplicate = dup_mig_pages_transferred();
> +    info->ram->skipped = skipped_mig_pages_transferred();
> +    info->ram->normal = norm_mig_pages_transferred();
> +    info->ram->normal_bytes = norm_mig_bytes_transferred();
> +    info->ram->mbps = s->mbps;
> +    info->ram->dirty_sync_count = s->dirty_sync_count;
> +
> +    if (s->state != MIGRATION_STATUS_COMPLETED) {
> +        info->ram->remaining = ram_bytes_remaining();
> +        info->ram->dirty_pages_rate = s->dirty_pages_rate;

In the 'else' case, shouldn't these be set to 0?

		Amit

  reply	other threads:[~2016-05-23  7:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 12:55 [Qemu-devel] [PATCH v4 0/6] postcopy (& 1 test) patch for 2.7 Dr. David Alan Gilbert (git)
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 1/6] Postcopy: Avoid 0 length discards Dr. David Alan Gilbert (git)
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 2/6] Migration: Split out ram part of qmp_query_migrate Dr. David Alan Gilbert (git)
2016-05-23  7:02   ` Amit Shah [this message]
2016-05-31 16:10     ` Dr. David Alan Gilbert
2016-06-01  3:48       ` Amit Shah
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 3/6] Postcopy: Add stats on page requests Dr. David Alan Gilbert (git)
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 4/6] test: Postcopy Dr. David Alan Gilbert (git)
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 5/6] tests: fix libqtest socket timeouts Dr. David Alan Gilbert (git)
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 6/6] Postcopy: Check for support when setting the capability Dr. David Alan Gilbert (git)

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=20160523070208.GA24417@grmbl.mre \
    --to=amit.shah@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=den@openvz.org \
    --cc=dgilbert@redhat.com \
    --cc=marcel.a@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 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.