qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>
To: Nikita Lapshin <nikita.lapshin@openvz.org>, qemu-devel@nongnu.org
Cc: den@openvz.org, Nikita Lapshin <nikita.lapshin@virtuozzo.com>
Subject: Re: [PATCH v1 6/8] migration: Add RAM part of migration stream
Date: Wed, 23 Mar 2022 16:52:52 +0300	[thread overview]
Message-ID: <7173cc21-004d-a25e-a787-1c7ee90dfba3@mail.ru> (raw)
In-Reply-To: <20220323105400.17649-7-nikita.lapshin@openvz.org>

23.03.2022 13:53, Nikita Lapshin wrote:
> From: Nikita Lapshin <nikita.lapshin@virtuozzo.com>
> 
> 'ram' parameter enable RAM sections in migration stream. If it
> isn't specified it will be skipped.
> 
> Signed-off-by: Nikita Lapshin <nikita.lapshin@openvz.org>
> ---
>   migration/migration.c | 17 ++++++++++++++++-
>   migration/migration.h |  1 +
>   migration/ram.c       |  6 ++++++
>   3 files changed, 23 insertions(+), 1 deletion(-)
> 
> diff --git a/migration/migration.c b/migration/migration.c
> index d81f3c6891..6528b3ad41 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -1339,7 +1339,8 @@ static bool check_stream_parts(strList *stream_list)
>       for (; stream_list; stream_list = stream_list->next) {
>           if (!strcmp(stream_list->value, "vmstate") ||
>               !strcmp(stream_list->value, "dirty-bitmaps") ||
> -            !strcmp(stream_list->value, "block")) {
> +            !strcmp(stream_list->value, "block") ||
> +            !strcmp(stream_list->value, "ram")) {
>               continue;
>           }
>   
> @@ -2653,6 +2654,20 @@ bool migrate_background_snapshot(void)
>       return s->enabled_capabilities[MIGRATION_CAPABILITY_BACKGROUND_SNAPSHOT];
>   }
>   
> +bool migrate_ram(void)
> +{
> +    MigrationState *s;
> +
> +    s = migrate_get_current();
> +
> +    /*
> +     * By default RAM is enabled so if stream-content-list disabled
> +     * RAM will be passed.
> +     */
> +    return !s->parameters.has_stream_content_list ||
> +           migrate_find_stream_content("ram");
> +}

I think, better is avoid this extra function

> +
>   /* Checks if stream-content parameter has section_name in list */
>   bool migrate_find_stream_content(const char *section_name)
>   {
> diff --git a/migration/migration.h b/migration/migration.h
> index 411c58e919..5c43788a2b 100644
> --- a/migration/migration.h
> +++ b/migration/migration.h
> @@ -395,6 +395,7 @@ int migrate_decompress_threads(void);
>   bool migrate_use_events(void);
>   bool migrate_postcopy_blocktime(void);
>   bool migrate_background_snapshot(void);
> +bool migrate_ram(void);
>   
>   bool migrate_find_stream_content(const char *section_name);
>   
> diff --git a/migration/ram.c b/migration/ram.c
> index 170e522a1f..ddc7abd08a 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -4263,6 +4263,11 @@ static int ram_resume_prepare(MigrationState *s, void *opaque)
>       return 0;
>   }
>   
> +static bool is_ram_active(void *opaque)
> +{
> +    return migrate_ram();

and here just call should_migrate_content("ram");

> +}
> +
>   static SaveVMHandlers savevm_ram_handlers = {
>       .save_setup = ram_save_setup,
>       .save_live_iterate = ram_save_iterate,
> @@ -4275,6 +4280,7 @@ static SaveVMHandlers savevm_ram_handlers = {
>       .load_setup = ram_load_setup,
>       .load_cleanup = ram_load_cleanup,
>       .resume_prepare = ram_resume_prepare,
> +    .is_active = is_ram_active,
>   };
>   
>   static void ram_mig_ram_block_resized(RAMBlockNotifier *n, void *host,


-- 
Best regards,
Vladimir


  parent reply	other threads:[~2022-03-23 13:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220323105400.17649-1-nikita.lapshin@openvz.org>
     [not found] ` <20220323105400.17649-2-nikita.lapshin@openvz.org>
2022-03-23 12:28   ` [PATCH v1 1/8] migration: Implemented new parameter stream_content Vladimir Sementsov-Ogievskiy
     [not found] ` <20220323105400.17649-3-nikita.lapshin@openvz.org>
2022-03-23 12:34   ` [PATCH v1 2/8] migration: should_skip() implemented Vladimir Sementsov-Ogievskiy
     [not found] ` <20220323105400.17649-4-nikita.lapshin@openvz.org>
2022-03-23 12:40   ` [PATCH v1 3/8] migration: Add vmstate part of migration stream Vladimir Sementsov-Ogievskiy
2022-03-23 12:49     ` Vladimir Sementsov-Ogievskiy
     [not found]       ` <f03bf2db-a424-17e2-38f1-1608c004c0e4@openvz.org>
2022-03-23 14:07         ` Vladimir Sementsov-Ogievskiy
     [not found] ` <20220323105400.17649-5-nikita.lapshin@openvz.org>
2022-03-23 12:49   ` [PATCH v1 4/8] migration: Add dirty-bitmaps " Vladimir Sementsov-Ogievskiy
     [not found] ` <20220323105400.17649-6-nikita.lapshin@openvz.org>
2022-03-23 12:50   ` [PATCH v1 5/8] migration: Add block " Vladimir Sementsov-Ogievskiy
     [not found] ` <20220323105400.17649-7-nikita.lapshin@openvz.org>
2022-03-23 13:52   ` Vladimir Sementsov-Ogievskiy [this message]
     [not found] ` <20220323105400.17649-8-nikita.lapshin@openvz.org>
2022-03-23 13:57   ` [PATCH v1 7/8] migration: analyze-migration script changed Vladimir Sementsov-Ogievskiy
2022-03-23 14:38     ` Nikita Lapshin
     [not found] ` <20220323105400.17649-9-nikita.lapshin@openvz.org>
2022-03-23 14:05   ` [PATCH v1 8/8] migration: Test for RAM and vmstate parts Vladimir Sementsov-Ogievskiy

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=7173cc21-004d-a25e-a787-1c7ee90dfba3@mail.ru \
    --to=v.sementsov-og@mail.ru \
    --cc=den@openvz.org \
    --cc=nikita.lapshin@openvz.org \
    --cc=nikita.lapshin@virtuozzo.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 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).