From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
Cc: Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Den Lunev <den@openvz.org>
Subject: Re: [PATCH v11 4/5] migration: implementation of background snapshot thread
Date: Tue, 19 Jan 2021 18:49:31 +0000 [thread overview]
Message-ID: <20210119184931.GJ3008@work-vm> (raw)
In-Reply-To: <20210106152120.31279-5-andrey.gruzdev@virtuozzo.com>
* Andrey Gruzdev (andrey.gruzdev@virtuozzo.com) 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.
I noticed there weren't any bdrv_ calls in here; I guess with a snapshot
you still have the source running so still have it accessing the disk;
do you do anything to try and wire the ram snapshotting up to disk
snapshotting?
> Signed-off-by: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
> Acked-by: Peter Xu <peterx@redhat.com>
> ---
> migration/migration.c | 255 +++++++++++++++++++++++++++++++++++++++++-
> migration/migration.h | 3 +
> migration/ram.c | 2 +
> migration/savevm.c | 1 -
> migration/savevm.h | 2 +
> 5 files changed, 260 insertions(+), 3 deletions(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index 2c2cb9ef01..0901a15ac5 100644
<snip>
> - qemu_thread_create(&s->thread, "live_migration", migration_thread, s,
> - QEMU_THREAD_JOINABLE);
> +
> + if (migrate_background_snapshot()) {
> + qemu_thread_create(&s->thread, "background_snapshot",
Unfortunately that wont work - there's a 14 character limit on
the thread name length; I guess we just shorten that to bg_snapshot
Other than that,
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> + bg_migration_thread, s, QEMU_THREAD_JOINABLE);
> + } else {
> + qemu_thread_create(&s->thread, "live_migration",
> + migration_thread, s, QEMU_THREAD_JOINABLE);
> + }
> s->migration_thread_running = true;
> }
>
> diff --git a/migration/migration.h b/migration/migration.h
> index f40338cfbf..0723955cd7 100644
> --- a/migration/migration.h
> +++ b/migration/migration.h
> @@ -20,6 +20,7 @@
> #include "qemu/thread.h"
> #include "qemu/coroutine_int.h"
> #include "io/channel.h"
> +#include "io/channel-buffer.h"
> #include "net/announce.h"
> #include "qom/object.h"
>
> @@ -147,8 +148,10 @@ struct MigrationState {
>
> /*< public >*/
> QemuThread thread;
> + QEMUBH *vm_start_bh;
> QEMUBH *cleanup_bh;
> QEMUFile *to_dst_file;
> + QIOChannelBuffer *bioc;
> /*
> * Protects to_dst_file pointer. We need to make sure we won't
> * yield or hang during the critical section, since this lock will
> diff --git a/migration/ram.c b/migration/ram.c
> index 5707382db1..05fe0c8592 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -1471,6 +1471,7 @@ static RAMBlock *poll_fault_page(RAMState *rs, ram_addr_t *offset)
> page_address = (void *) uffd_msg.arg.pagefault.address;
> bs = qemu_ram_block_from_host(page_address, false, offset);
> assert(bs && (bs->flags & RAM_UF_WRITEPROTECT) != 0);
> +
> return bs;
> }
> #endif /* CONFIG_LINUX */
> @@ -1836,6 +1837,7 @@ static void ram_save_host_page_post(RAMState *rs, PageSearchStatus *pss,
> /* Un-protect memory range. */
> res = uffd_change_protection(rs->uffdio_fd, page_address, run_length,
> false, false);
> +
> /* We don't want to override existing error from ram_save_host_page(). */
> if (res < 0 && *res_override >= 0) {
> *res_override = res;
> diff --git a/migration/savevm.c b/migration/savevm.c
> index 27e842812e..dd4ad0aaaf 100644
> --- a/migration/savevm.c
> +++ b/migration/savevm.c
> @@ -1354,7 +1354,6 @@ int qemu_savevm_state_complete_precopy_iterable(QEMUFile *f, bool in_postcopy)
> return 0;
> }
>
> -static
> int qemu_savevm_state_complete_precopy_non_iterable(QEMUFile *f,
> bool in_postcopy,
> bool inactivate_disks)
> diff --git a/migration/savevm.h b/migration/savevm.h
> index ba64a7e271..aaee2528ed 100644
> --- a/migration/savevm.h
> +++ b/migration/savevm.h
> @@ -64,5 +64,7 @@ int qemu_loadvm_state(QEMUFile *f);
> void qemu_loadvm_state_cleanup(void);
> int qemu_loadvm_state_main(QEMUFile *f, MigrationIncomingState *mis);
> int qemu_load_device_state(QEMUFile *f);
> +int qemu_savevm_state_complete_precopy_non_iterable(QEMUFile *f,
> + bool in_postcopy, bool inactivate_disks);
>
> #endif
> --
> 2.25.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2021-01-19 19:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 15:21 [PATCH v11 0/5] UFFD write-tracking migration/snapshots Andrey Gruzdev via
2021-01-06 15:21 ` [PATCH v11 1/5] migration: introduce 'background-snapshot' migration capability Andrey Gruzdev via
2021-01-06 15:21 ` [PATCH v11 2/5] migration: introduce UFFD-WP low-level interface helpers Andrey Gruzdev via
2021-01-06 15:21 ` [PATCH v11 3/5] migration: support UFFD write fault processing in ram_save_iterate() Andrey Gruzdev via
2021-01-19 17:49 ` Dr. David Alan Gilbert
2021-01-21 8:48 ` Andrey Gruzdev
2021-01-21 10:09 ` Dr. David Alan Gilbert
2021-01-21 11:12 ` Andrey Gruzdev
2021-01-06 15:21 ` [PATCH v11 4/5] migration: implementation of background snapshot thread Andrey Gruzdev via
2021-01-19 18:49 ` Dr. David Alan Gilbert [this message]
2021-01-21 8:58 ` Andrey Gruzdev
2021-01-21 9:56 ` Dr. David Alan Gilbert
2021-01-21 11:08 ` Andrey Gruzdev
2021-01-21 16:11 ` Dr. David Alan Gilbert
2021-01-21 17:28 ` Andrey Gruzdev
2021-01-21 17:48 ` Dr. David Alan Gilbert
2021-01-21 18:29 ` Andrey Gruzdev
2021-01-06 15:21 ` [PATCH v11 5/5] migration: introduce 'userfaultfd-wrlat.py' script Andrey Gruzdev via
2021-01-19 21:01 ` Peter Xu
2021-01-21 13:12 ` Andrey Gruzdev
2021-01-21 15:37 ` Peter Xu
2021-01-21 17:15 ` Andrey Gruzdev
2021-01-15 11:34 ` [PATCH v11 0/5] UFFD write-tracking migration/snapshots Andrey Gruzdev
2021-01-15 14:54 ` Peter Xu
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=20210119184931.GJ3008@work-vm \
--to=dgilbert@redhat.com \
--cc=andrey.gruzdev@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=pbonzini@redhat.com \
--cc=peterx@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).