From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] migration/postcopy: cleanup function postcopy_send_discard_bm_ram
Date: Wed, 7 Aug 2019 18:16:05 +0100 [thread overview]
Message-ID: <20190807171605.GD27871@work-vm> (raw)
In-Reply-To: <20190627020822.15485-1-richardw.yang@linux.intel.com>
* Wei Yang (richardw.yang@linux.intel.com) wrote:
> Some cleanup of function postcopy_send_discard_bm_ram:
>
> * use a more restrict check for discard page
> * break the loop when no more page to discard
> * it is for sure discard_length is not 0
>
> No functional change.
>
Queued
> Wei Yang (3):
> migration/postcopy: the valid condition is one less then end
> migration/postcopy: break the loop when there is no more page to
> discard
> migration/postcopy: discard_length must not be 0
>
> migration/ram.c | 24 +++++++++++-------------
> 1 file changed, 11 insertions(+), 13 deletions(-)
>
> --
> 2.19.1
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2019-08-07 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 2:08 [Qemu-devel] [PATCH 0/3] migration/postcopy: cleanup function postcopy_send_discard_bm_ram Wei Yang
2019-06-27 2:08 ` [Qemu-devel] [PATCH 1/3] migration/postcopy: the valid condition is one less then end Wei Yang
2019-06-28 15:09 ` Dr. David Alan Gilbert
2019-06-28 23:04 ` Wei Yang
2019-06-27 2:08 ` [Qemu-devel] [PATCH 2/3] migration/postcopy: break the loop when there is no more page to discard Wei Yang
2019-06-28 15:15 ` Dr. David Alan Gilbert
2019-06-27 2:08 ` [Qemu-devel] [PATCH 3/3] migration/postcopy: discard_length must not be 0 Wei Yang
2019-06-28 15:17 ` Dr. David Alan Gilbert
2019-08-07 17:16 ` Dr. David Alan Gilbert [this message]
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=20190807171605.GD27871@work-vm \
--to=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richardw.yang@linux.intel.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).