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 v5 4/4] migration: implementation of background snapshot thread
Date: Tue, 8 Dec 2020 13:16:00 -0500 [thread overview]
Message-ID: <20201208181600.GD21402@xz-x1> (raw)
In-Reply-To: <20201204093103.9878-5-andrey.gruzdev@virtuozzo.com>
On Fri, Dec 04, 2020 at 12:31:03PM +0300, Andrey Gruzdev wrote:
> Introducing implementation of 'background' snapshot thread
> which in overall follows the logic of precopy migration
> while internally utilizes completely different mechanism
> to 'freeze' vmstate at the start of snapshot creation.
>
> This mechanism is based on userfault_fd with wr-protection
> support and is Linux-specific.
>
> Signed-off-by: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2020-12-08 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 9:30 [PATCH v5 0/4] migration: UFFD write-tracking migration/snapshots Andrey Gruzdev via
2020-12-04 9:31 ` [PATCH v5 1/4] migration: introduce 'background-snapshot' migration capability Andrey Gruzdev via
2020-12-08 15:47 ` Peter Xu
2020-12-09 7:08 ` Andrey Gruzdev
2020-12-04 9:31 ` [PATCH v5 2/4] migration: introduce UFFD-WP low-level interface helpers Andrey Gruzdev via
2020-12-08 17:57 ` Peter Xu
2020-12-04 9:31 ` [PATCH v5 3/4] migration: support UFFD write fault processing in ram_save_iterate() Andrey Gruzdev via
2020-12-08 18:09 ` Peter Xu
2020-12-04 9:31 ` [PATCH v5 4/4] migration: implementation of background snapshot thread Andrey Gruzdev via
2020-12-08 18:16 ` Peter Xu [this message]
2020-12-08 18:24 ` [PATCH v5 0/4] migration: UFFD write-tracking migration/snapshots Peter Xu
2020-12-09 7:17 ` 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=20201208181600.GD21402@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).