From: Peter Xu <peterx@redhat.com>
To: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
Cc: Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Den Lunev <den@openvz.org>
Subject: Re: [PATCH v10 0/5] UFFD write-tracking migration/snapshots
Date: Mon, 21 Dec 2020 10:17:25 -0500 [thread overview]
Message-ID: <20201221151725.GA6640@xz-x1> (raw)
In-Reply-To: <594af923-f960-5e8c-ec14-ef43d8ede8c9@virtuozzo.com>
On Mon, Dec 21, 2020 at 03:44:38PM +0300, Andrey Gruzdev wrote:
> Hi Peter,
>
> I have a question about the Wiki page you've created https://wiki.qemu.org/ToDo/LiveMigration#Features.
> May we also add to that page/have access rights?
Yes. I'll send you another email soon for that. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2020-12-21 15:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 16:57 [PATCH v10 0/5] UFFD write-tracking migration/snapshots Andrey Gruzdev via
2020-12-17 16:57 ` [PATCH v10 1/5] migration: introduce 'background-snapshot' migration capability Andrey Gruzdev via
2020-12-17 16:57 ` [PATCH v10 2/5] migration: introduce UFFD-WP low-level interface helpers Andrey Gruzdev via
2020-12-17 16:57 ` [PATCH v10 3/5] migration: support UFFD write fault processing in ram_save_iterate() Andrey Gruzdev via
2020-12-17 16:57 ` [PATCH v10 4/5] migration: implementation of background snapshot thread Andrey Gruzdev via
2020-12-17 16:57 ` [PATCH v10 5/5] migration: introduce 'userfaultfd-wrlat.py' script Andrey Gruzdev via
2020-12-21 12:44 ` [PATCH v10 0/5] UFFD write-tracking migration/snapshots Andrey Gruzdev
2020-12-21 15:17 ` Peter Xu [this message]
2020-12-21 15:36 ` Andrey Gruzdev
2020-12-21 14:52 ` Andrey Gruzdev
2021-01-05 19:36 ` Peter Xu
2021-01-06 15:19 ` Andrey Gruzdev
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=20201221151725.GA6640@xz-x1 \
--to=peterx@redhat.com \
--cc=andrey.gruzdev@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=pbonzini@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 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).