From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Andrea Arcangeli <aarcange@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Alexey Perevalov <a.perevalov@samsung.com>
Subject: Re: [Qemu-devel] [PATCH v7 17/23] migration: setup ramstate for resume
Date: Mon, 12 Mar 2018 17:30:12 +0000 [thread overview]
Message-ID: <20180312173011.GT3219@work-vm> (raw)
In-Reply-To: <20180309091535.13315-18-peterx@redhat.com>
* Peter Xu (peterx@redhat.com) wrote:
> After we updated the dirty bitmaps of ramblocks, we also need to update
> the critical fields in RAMState to make sure it is ready for a resume.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> migration/ram.c | 45 ++++++++++++++++++++++++++++++++++++++++++++-
> migration/trace-events | 1 +
> 2 files changed, 45 insertions(+), 1 deletion(-)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 196b1ba876..5cd9f43728 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -2254,6 +2254,41 @@ static int ram_init_all(RAMState **rsp)
> return 0;
> }
>
> +static void ram_state_resume_prepare(RAMState *rs, QEMUFile *out)
> +{
> + RAMBlock *block;
> + uint64_t pages = 0;
> +
> + /*
> + * Postcopy is not using xbzrle/compression, so no need for that.
> + * Also, since source are already halted, we don't need to care
> + * about dirty page logging as well.
> + */
> +
> + RAMBLOCK_FOREACH(block) {
> + pages += bitmap_count_one(block->bmap,
> + block->used_length >> TARGET_PAGE_BITS);
> + }
> +
> + /* This may not be aligned with current bitmaps. Recalculate. */
> + rs->migration_dirty_pages = pages;
> +
> + rs->last_seen_block = NULL;
> + rs->last_sent_block = NULL;
> + rs->last_page = 0;
> + rs->last_version = ram_list.version;
> + /*
> + * Disable the bulk stage, otherwise we'll resend the whole RAM no
> + * matter what we have sent.
> + */
> + rs->ram_bulk_stage = false;
> +
> + /* Update RAMState cache of output QEMUFile */
> + rs->f = out;
> +
> + trace_ram_state_resume_prepare(pages);
> +}
> +
> /*
> * Each of ram_save_setup, ram_save_iterate and ram_save_complete has
> * long-running RCU critical section. When rcu-reclaims in the code
> @@ -3182,8 +3217,16 @@ out:
> static int ram_resume_prepare(MigrationState *s, void *opaque)
> {
> RAMState *rs = *(RAMState **)opaque;
> + int ret;
>
> - return ram_dirty_bitmap_sync_all(s, rs);
> + ret = ram_dirty_bitmap_sync_all(s, rs);
> + if (ret) {
> + return ret;
> + }
> +
> + ram_state_resume_prepare(rs, s->to_dst_file);
> +
> + return 0;
> }
>
> static SaveVMHandlers savevm_ram_handlers = {
> diff --git a/migration/trace-events b/migration/trace-events
> index 45b1d89217..f5913ff51c 100644
> --- a/migration/trace-events
> +++ b/migration/trace-events
> @@ -88,6 +88,7 @@ ram_dirty_bitmap_reload_complete(char *str) "%s"
> ram_dirty_bitmap_sync_start(void) ""
> ram_dirty_bitmap_sync_wait(void) ""
> ram_dirty_bitmap_sync_complete(void) ""
> +ram_state_resume_prepare(long v) "%ld"
Actually, just noticed that's a long but the values passed is now
uint64_t - be careful.
Dave
> # migration/migration.c
> await_return_path_close_on_source_close(void) ""
> --
> 2.14.3
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-03-12 17:30 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 9:15 [Qemu-devel] [PATCH v7 00/23] Migration: postcopy failure recovery Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 01/23] migration: let incoming side use thread context Peter Xu
2018-03-12 17:27 ` Dr. David Alan Gilbert
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 02/23] migration: new postcopy-pause state Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 03/23] migration: implement "postcopy-pause" src logic Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 04/23] migration: allow dst vm pause on postcopy Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 05/23] migration: allow src return path to pause Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 06/23] migration: allow fault thread " Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 07/23] qmp: hmp: add migrate "resume" option Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 08/23] migration: rebuild channel on source Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 09/23] migration: new state "postcopy-recover" Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 10/23] migration: wakeup dst ram-load-thread for recover Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 11/23] migration: new cmd MIG_CMD_RECV_BITMAP Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 12/23] migration: new message MIG_RP_MSG_RECV_BITMAP Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 13/23] migration: new cmd MIG_CMD_POSTCOPY_RESUME Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 14/23] migration: new message MIG_RP_MSG_RESUME_ACK Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 15/23] migration: introduce SaveVMHandlers.resume_prepare Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 16/23] migration: synchronize dirty bitmap for resume Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 17/23] migration: setup ramstate " Peter Xu
2018-03-12 17:29 ` Dr. David Alan Gilbert
2018-03-12 17:30 ` Dr. David Alan Gilbert [this message]
2018-03-13 8:36 ` Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 18/23] migration: final handshake for the resume Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 19/23] migration: init dst in migration_object_init too Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 20/23] qmp/migration: new command migrate-recover Peter Xu
2018-03-12 17:33 ` Dr. David Alan Gilbert
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 21/23] hmp/migration: add migrate_recover command Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 22/23] migration/qmp: add command migrate-pause Peter Xu
2018-03-12 17:36 ` Dr. David Alan Gilbert
2018-03-13 8:54 ` Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 23/23] migration/hmp: add migrate_pause command Peter Xu
2018-03-09 9:47 ` [Qemu-devel] [PATCH v7 00/23] Migration: postcopy failure recovery no-reply
2018-03-09 9:48 ` no-reply
2018-03-09 9:49 ` no-reply
2018-03-09 9:51 ` no-reply
2018-03-09 9:56 ` no-reply
2018-03-09 9:57 ` no-reply
2018-03-09 16:54 ` Eric Blake
2018-03-09 16:59 ` Eric Blake
2018-03-12 4:45 ` Peter Xu
2018-03-15 8:19 ` Fam Zheng
2018-03-15 8:41 ` Peter Xu
2018-03-15 9:04 ` Fam Zheng
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=20180312173011.GT3219@work-vm \
--to=dgilbert@redhat.com \
--cc=a.perevalov@samsung.com \
--cc=aarcange@redhat.com \
--cc=berrange@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).