From: Juan Quintela <quintela@redhat.com>
To: Alexey Perevalov <a.perevalov@samsung.com>
Cc: qemu-devel@nongnu.org, i.maximets@samsung.com, peterx@redhat.com,
dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH v8 08/11] migration: postcopy_place_page factoring out
Date: Wed, 07 Jun 2017 14:58:40 +0200 [thread overview]
Message-ID: <87h8zseyyn.fsf@secure.mitica> (raw)
In-Reply-To: <1496828798-27548-9-git-send-email-a.perevalov@samsung.com> (Alexey Perevalov's message of "Wed, 07 Jun 2017 12:46:35 +0300")
Alexey Perevalov <a.perevalov@samsung.com> wrote:
> Need to mark paged copied as closer as possible place where it
> tracks down. That will be necessary in futher patch.
>
> Signed-off-by: Alexey Perevalov <a.perevalov@samsung.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
next prev parent reply other threads:[~2017-06-07 12:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170607094720eucas1p24650bb7bb139ae209fc0ea8c5c57534b@eucas1p2.samsung.com>
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 00/11] calculate blocktime for postcopy live migration Alexey Perevalov
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 01/11] userfault: add pid into uffd_msg & update UFFD_FEATURE_* Alexey Perevalov
2017-06-12 12:27 ` Dr. David Alan Gilbert
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 02/11] migration: pass MigrationIncomingState* into migration check functions Alexey Perevalov
2017-06-09 4:10 ` Peter Xu
2017-06-09 6:21 ` Alexey Perevalov
2017-06-09 7:14 ` Peter Xu
2017-06-09 7:25 ` Alexey Perevalov
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 03/11] migration: fix hardcoded function name in error report Alexey Perevalov
2017-06-07 12:31 ` Juan Quintela
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 04/11] migration: split ufd_version_check onto receive/request features part Alexey Perevalov
2017-06-12 9:52 ` Dr. David Alan Gilbert
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 05/11] migration: introduce postcopy-blocktime capability Alexey Perevalov
2017-06-07 12:34 ` Juan Quintela
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 06/11] migration: add postcopy blocktime ctx into MigrationIncomingState Alexey Perevalov
2017-06-07 12:43 ` Juan Quintela
2017-06-07 12:53 ` Alexey Perevalov
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 07/11] migration: add bitmap for copied page Alexey Perevalov
2017-06-07 12:56 ` Juan Quintela
2017-06-07 14:46 ` Alexey Perevalov
2017-06-07 14:13 ` Alexey Perevalov
2017-06-09 6:06 ` Peter Xu
2017-06-09 7:16 ` Alexey Perevalov
2017-06-12 11:11 ` Dr. David Alan Gilbert
2017-06-13 5:59 ` Peter Xu
2017-06-13 6:10 ` Alexey Perevalov
2017-06-13 6:23 ` Peter Xu
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 08/11] migration: postcopy_place_page factoring out Alexey Perevalov
2017-06-07 12:58 ` Juan Quintela [this message]
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 09/11] migration: calculate vCPU blocktime on dst side Alexey Perevalov
2017-06-07 13:11 ` Juan Quintela
2017-06-12 11:34 ` Dr. David Alan Gilbert
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 10/11] migration: add postcopy total blocktime into query-migrate Alexey Perevalov
2017-06-07 9:46 ` [Qemu-devel] [PATCH v8 11/11] migration: postcopy_blocktime documentation Alexey Perevalov
2017-06-07 12:52 ` Juan Quintela
2017-06-07 13:08 ` Alexey Perevalov
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=87h8zseyyn.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=a.perevalov@samsung.com \
--cc=dgilbert@redhat.com \
--cc=i.maximets@samsung.com \
--cc=peterx@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.