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: [PATCH 0/2] migration/postcopy: map tmp and large zero page in setup stage
Date: Fri, 11 Oct 2019 14:29:03 +0100 [thread overview]
Message-ID: <20191011132903.GD18007@work-vm> (raw)
In-Reply-To: <20191005135021.21721-1-richardw.yang@linux.intel.com>
* Wei Yang (richardw.yang@linux.intel.com) wrote:
> Currently we map these page when we want to use it, while this may be a
> little late.
>
> To make the code consistency, these two patches move the map into
> postcopy_ram_incoming_setup.
Queued
>
> Wei Yang (2):
> migration/postcopy: allocate tmp_page in setup stage
> migration/postcopy: map large zero page in
> postcopy_ram_incoming_setup()
>
> migration/postcopy-ram.c | 74 +++++++++++++++-------------------------
> migration/postcopy-ram.h | 7 ----
> migration/ram.c | 2 +-
> 3 files changed, 28 insertions(+), 55 deletions(-)
>
> --
> 2.17.1
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2019-10-11 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 13:50 [PATCH 0/2] migration/postcopy: map tmp and large zero page in setup stage Wei Yang
2019-10-05 13:50 ` [PATCH 1/2] migration/postcopy: allocate tmp_page " Wei Yang
2019-10-08 17:18 ` Dr. David Alan Gilbert
2019-10-05 13:50 ` [PATCH 2/2] migration/postcopy: map large zero page in postcopy_ram_incoming_setup() Wei Yang
2019-10-08 17:24 ` Dr. David Alan Gilbert
2019-10-09 1:10 ` Wei Yang
2019-10-11 10:15 ` Dr. David Alan Gilbert
2019-10-11 13:29 ` 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=20191011132903.GD18007@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 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.