xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH for 4.6 v2 2/5] libxc: migration v2 prefix Memory -> Frames
Date: Sun, 6 Sep 2015 20:21:00 +0100	[thread overview]
Message-ID: <20150906192100.GA30249@zion.uk.xensource.com> (raw)
In-Reply-To: <55EC689D.4080902@citrix.com>

On Sun, Sep 06, 2015 at 05:23:57PM +0100, Andrew Cooper wrote:
> On 05/09/15 00:59, Wei Liu wrote:
> >The prefix "Memory" is confusing because the numbers shown after that
> >are referring to frames. They have no bearing on how many pages a domain
> >actually owns or how many actual pages are processed.
> 
> There is a direct bearing on how many pages are processed, by virtue of the
> "$X of $Y" later in the line.  I think your final phrase is misleading and
> should just be dropped.
> 

OK.

> Also, there are two further places which need "Memory" changing in a similar
> way; send_memory_verify() (which itself should probably be renamed to
> verify_frames()), and update_progress_string() which is the companion to the
> hunk below, but for live migration.
> 

I will fix those, too.

Wei.

> ~Andrew
> 
> >
> >Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> >---
> >  tools/libxc/xc_sr_save.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/tools/libxc/xc_sr_save.c b/tools/libxc/xc_sr_save.c
> >index 58667af..924c425 100644
> >--- a/tools/libxc/xc_sr_save.c
> >+++ b/tools/libxc/xc_sr_save.c
> >@@ -659,7 +659,7 @@ static int send_domain_memory_nonlive(struct xc_sr_context *ctx)
> >      if ( rc )
> >          goto err;
> >-    xc_set_progress_prefix(xch, "Memory");
> >+    xc_set_progress_prefix(xch, "Frames");
> >      rc = send_all_pages(ctx);
> >      if ( rc )

  reply	other threads:[~2015-09-06 19:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 23:59 [PATCH for 4.6 v2 0/5] Migration v2 fix Wei Liu
2015-09-04 23:59 ` [PATCH for 4.6 v2 1/5] libxc: clearer migration v2 debug message Wei Liu
2015-09-04 23:59 ` [PATCH for 4.6 v2 2/5] libxc: migration v2 prefix Memory -> Frames Wei Liu
2015-09-06 16:23   ` Andrew Cooper
2015-09-06 19:21     ` Wei Liu [this message]
2015-09-04 23:59 ` [PATCH for 4.6 v2 3/5] libxc: fix indentation Wei Liu
2015-09-04 23:59 ` [PATCH for 4.6 v2 4/5] libxc: don't populate same pfn more than once in populate_pfns Wei Liu
2015-09-06 16:25   ` Andrew Cooper
2015-09-04 23:59 ` [PATCH for 4.6 v2 5/5] libxc: add assertion to avoid setting same bit more than once Wei Liu

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=20150906192100.GA30249@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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).