From: "Leonardo Brás" <leobras@redhat.com>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: "Peter Xu" <peterx@redhat.com>, "Greg Kurz" <groug@kaod.org>,
qemu-s390x@nongnu.org, "Fam Zheng" <fam@euphon.net>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Halil Pasic" <pasic@linux.ibm.com>,
"John Snow" <jsnow@redhat.com>,
qemu-ppc@nongnu.org,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"David Hildenbrand" <david@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Eric Farman" <farman@linux.ibm.com>,
qemu-block@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
"Eric Blake" <eblake@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>
Subject: Re: [PATCH v2 03/16] migration: Move setup_time to mig_stats
Date: Wed, 24 May 2023 22:18:27 -0300 [thread overview]
Message-ID: <35a04e2de57e02745c18076990ce63fa6f61f5a4.camel@redhat.com> (raw)
In-Reply-To: <20230515195709.63843-4-quintela@redhat.com>
On Mon, 2023-05-15 at 21:56 +0200, Juan Quintela wrote:
> It is a time that needs to be cleaned each time cancel migration.
> Once there create migration_time_since() to calculate how time since a
> time in the past.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
>
> ---
>
> Rename to migration_time_since (cédric)
> ---
> migration/migration-stats.h | 13 +++++++++++++
> migration/migration.h | 1 -
> migration/migration-stats.c | 7 +++++++
> migration/migration.c | 9 ++++-----
> 4 files changed, 24 insertions(+), 6 deletions(-)
>
> diff --git a/migration/migration-stats.h b/migration/migration-stats.h
> index e782f1b0df..21402af9e4 100644
> --- a/migration/migration-stats.h
> +++ b/migration/migration-stats.h
> @@ -75,6 +75,10 @@ typedef struct {
> * Number of bytes sent during precopy stage.
> */
> Stat64 precopy_bytes;
> + /*
> + * How long has the setup stage took.
> + */
> + Stat64 setup_time;
> /*
> * Total number of bytes transferred.
> */
> @@ -87,4 +91,13 @@ typedef struct {
>
> extern MigrationAtomicStats mig_stats;
>
> +/**
> + * migration_time_since: Calculate how much time has passed
> + *
> + * @stats: migration stats
> + * @since: reference time since we want to calculate
> + *
> + * Returns: Nothing. The time is stored in val.
> + */
> +void migration_time_since(MigrationAtomicStats *stats, int64_t since);
> #endif
> diff --git a/migration/migration.h b/migration/migration.h
> index 48a46123a0..27aa3b1035 100644
> --- a/migration/migration.h
> +++ b/migration/migration.h
> @@ -316,7 +316,6 @@ struct MigrationState {
> int64_t downtime;
> int64_t expected_downtime;
> bool capabilities[MIGRATION_CAPABILITY__MAX];
> - int64_t setup_time;
> /*
> * Whether guest was running when we enter the completion stage.
> * If migration is interrupted by any reason, we need to continue
> diff --git a/migration/migration-stats.c b/migration/migration-stats.c
> index 2f2cea965c..3431453c90 100644
> --- a/migration/migration-stats.c
> +++ b/migration/migration-stats.c
> @@ -12,6 +12,13 @@
>
> #include "qemu/osdep.h"
> #include "qemu/stats64.h"
> +#include "qemu/timer.h"
> #include "migration-stats.h"
>
> MigrationAtomicStats mig_stats;
> +
> +void migration_time_since(MigrationAtomicStats *stats, int64_t since)
> +{
> + int64_t now = qemu_clock_get_ms(QEMU_CLOCK_HOST);
> + stat64_set(&stats->setup_time, now - since);
> +}
IIUC this calculates a time delta and saves on stats->setup_time, is that right?
It took me some time to understand that, since the function name is
migration_time_since(), which seems more generic.
Would not be more intuitive to name it migration_setup_time_set() or so?
Anyway,
Reviewed-by: Leonardo Bras <leobras@redhat.com>
> diff --git a/migration/migration.c b/migration/migration.c
> index c41c7491bb..e9466273bb 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -887,7 +887,7 @@ static void populate_time_info(MigrationInfo *info, MigrationState *s)
> {
> info->has_status = true;
> info->has_setup_time = true;
> - info->setup_time = s->setup_time;
> + info->setup_time = stat64_get(&mig_stats.setup_time);
>
> if (s->state == MIGRATION_STATUS_COMPLETED) {
> info->has_total_time = true;
> @@ -1390,7 +1390,6 @@ void migrate_init(MigrationState *s)
> s->pages_per_second = 0.0;
> s->downtime = 0;
> s->expected_downtime = 0;
> - s->setup_time = 0;
I could not see MigrationState->setup_time being initialized as 0 in this patch.
In a quick look in the code I noticed there is no initialization of this struct,
but on qemu_savevm_state() and migrate_prepare() we have:
memset(&mig_stats, 0, sizeof(mig_stats));
I suppose this is enough, right?
> s->start_postcopy = false;
> s->postcopy_after_devices = false;
> s->migration_thread_running = false;
> @@ -2647,7 +2646,7 @@ static void migration_calculate_complete(MigrationState *s)
> s->downtime = end_time - s->downtime_start;
> }
>
> - transfer_time = s->total_time - s->setup_time;
> + transfer_time = s->total_time - stat64_get(&mig_stats.setup_time);
> if (transfer_time) {
> s->mbps = ((double) bytes * 8.0) / transfer_time / 1000;
> }
> @@ -2969,7 +2968,7 @@ static void *migration_thread(void *opaque)
> qemu_savevm_wait_unplug(s, MIGRATION_STATUS_SETUP,
> MIGRATION_STATUS_ACTIVE);
>
> - s->setup_time = qemu_clock_get_ms(QEMU_CLOCK_HOST) - setup_start;
> + migration_time_since(&mig_stats, setup_start);
>
> trace_migration_thread_setup_complete();
>
> @@ -3081,7 +3080,7 @@ static void *bg_migration_thread(void *opaque)
> qemu_savevm_wait_unplug(s, MIGRATION_STATUS_SETUP,
> MIGRATION_STATUS_ACTIVE);
>
> - s->setup_time = qemu_clock_get_ms(QEMU_CLOCK_HOST) - setup_start;
> + migration_time_since(&mig_stats, setup_start);
>
> trace_migration_thread_setup_complete();
> s->downtime_start = qemu_clock_get_ms(QEMU_CLOCK_REALTIME);
next prev parent reply other threads:[~2023-05-25 1:19 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 19:56 [PATCH v2 00/16] Migration: More migration atomic counters Juan Quintela
2023-05-15 19:56 ` [PATCH v2 01/16] migration: Don't use INT64_MAX for unlimited rate Juan Quintela
2023-05-16 4:49 ` Harsh Prateek Bora
2023-05-16 9:13 ` David Edmondson
2023-05-16 9:24 ` Juan Quintela
2023-05-16 9:55 ` David Edmondson
2023-05-16 12:47 ` Cédric Le Goater
2023-05-23 1:57 ` Leonardo Brás
2023-05-15 19:56 ` [PATCH v2 02/16] migration: Correct transferred bytes value Juan Quintela
2023-05-16 9:35 ` David Edmondson
2023-05-23 2:15 ` Leonardo Brás
2023-05-26 8:04 ` Juan Quintela
2023-05-26 18:50 ` Leonardo Bras Soares Passos
2023-05-30 10:30 ` Juan Quintela
2023-05-15 19:56 ` [PATCH v2 03/16] migration: Move setup_time to mig_stats Juan Quintela
2023-05-16 9:42 ` David Edmondson
2023-05-16 10:06 ` Juan Quintela
2023-05-16 11:07 ` David Edmondson
2023-05-25 1:18 ` Leonardo Brás [this message]
2023-05-26 8:07 ` Juan Quintela
2023-05-26 18:53 ` Leonardo Bras Soares Passos
2023-05-15 19:56 ` [PATCH v2 04/16] qemu-file: Account for rate_limit usage on qemu_fflush() Juan Quintela
2023-05-25 1:33 ` Leonardo Brás
2023-05-26 8:09 ` Juan Quintela
2023-05-26 18:54 ` Leonardo Bras Soares Passos
2023-05-15 19:56 ` [PATCH v2 05/16] migration: Move rate_limit_max and rate_limit_used to migration_stats Juan Quintela
2023-05-16 12:43 ` Cédric Le Goater
2023-05-25 3:06 ` Leonardo Brás
2023-05-15 19:56 ` [PATCH v2 06/16] migration: Move migration_total_bytes() to migration-stats.c Juan Quintela
2023-05-25 3:09 ` Leonardo Brás
2023-05-15 19:57 ` [PATCH v2 07/16] migration: Add a trace for migration_transferred_bytes Juan Quintela
2023-05-25 3:18 ` Leonardo Brás
2023-05-15 19:57 ` [PATCH v2 08/16] migration: Use migration_transferred_bytes() to calculate rate_limit Juan Quintela
2023-05-25 6:50 ` Leonardo Brás
2023-05-26 8:17 ` Juan Quintela
2023-05-26 18:59 ` Leonardo Bras Soares Passos
2023-05-15 19:57 ` [PATCH v2 09/16] migration: We don't need the field rate_limit_used anymore Juan Quintela
2023-05-25 6:50 ` Leonardo Brás
2023-05-26 8:18 ` Juan Quintela
2023-05-26 18:59 ` Leonardo Bras Soares Passos
2023-05-15 19:57 ` [PATCH v2 10/16] migration: Don't abuse qemu_file transferred for RDMA Juan Quintela
2023-05-25 6:53 ` Leonardo Brás
2023-05-15 19:57 ` [PATCH v2 11/16] migration/RDMA: It is accounting for zero/normal pages in two places Juan Quintela
2023-05-25 7:06 ` Leonardo Brás
2023-05-15 19:57 ` [PATCH v2 12/16] migration/rdma: Remove QEMUFile parameter when not used Juan Quintela
2023-05-25 7:21 ` Leonardo Brás
2023-05-15 19:57 ` [PATCH v2 13/16] migration/rdma: Don't use imaginary transfers Juan Quintela
2023-05-25 7:27 ` Leonardo Brás
2023-05-15 19:57 ` [PATCH v2 14/16] migration: Remove unused qemu_file_credit_transfer() Juan Quintela
2023-05-25 7:29 ` Leonardo Brás
2023-05-15 19:57 ` [PATCH v2 15/16] migration/rdma: Simplify the function that saves a page Juan Quintela
2023-05-25 8:10 ` Leonardo Brás
2023-05-26 8:21 ` Juan Quintela
2023-05-26 19:03 ` Leonardo Bras Soares Passos
2023-05-15 19:57 ` [PATCH v2 16/16] migration/multifd: Compute transferred bytes correctly Juan Quintela
2023-05-25 8:38 ` Leonardo Brás
2023-05-26 8:23 ` Juan Quintela
2023-05-26 19:04 ` Leonardo Bras Soares Passos
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=35a04e2de57e02745c18076990ce63fa6f61f5a4.camel@redhat.com \
--to=leobras@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=farman@linux.ibm.com \
--cc=groug@kaod.org \
--cc=harshpb@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=jsnow@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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).