From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Juan Quintela <quintela@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
Lukas Straub <lukasstraub2@web.de>
Subject: [PULL 4/8] migration: Rename RAMStats to MigrationAtomicStats
Date: Wed, 3 May 2023 11:26:02 +0200 [thread overview]
Message-ID: <20230503092606.9415-5-quintela@redhat.com> (raw)
In-Reply-To: <20230503092606.9415-1-quintela@redhat.com>
It is lousely based on MigrationStats, but that name is taken, so this
is the best one that I came with.
Signed-off-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Lukas Straub <lukasstraub2@web.de>
---
If you have any good suggestion for the name, I am all ears.
---
migration/migration-stats.c | 2 +-
migration/migration-stats.h | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/migration/migration-stats.c b/migration/migration-stats.c
index 8c0af9b80a..2f2cea965c 100644
--- a/migration/migration-stats.c
+++ b/migration/migration-stats.c
@@ -14,4 +14,4 @@
#include "qemu/stats64.h"
#include "migration-stats.h"
-RAMStats mig_stats;
+MigrationAtomicStats mig_stats;
diff --git a/migration/migration-stats.h b/migration/migration-stats.h
index 197374b4f6..149af932d7 100644
--- a/migration/migration-stats.h
+++ b/migration/migration-stats.h
@@ -34,8 +34,8 @@ typedef struct {
Stat64 postcopy_requests;
Stat64 precopy_bytes;
Stat64 transferred;
-} RAMStats;
+} MigrationAtomicStats;
-extern RAMStats mig_stats;
+extern MigrationAtomicStats mig_stats;
#endif
--
2.40.0
next prev parent reply other threads:[~2023-05-03 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 9:25 [PULL 0/8] Migration 20230428 patches Juan Quintela
2023-05-03 9:25 ` [PULL 1/8] multifd: We already account for this packet on the multifd thread Juan Quintela
2023-05-03 9:26 ` [PULL 2/8] migration: Move ram_stats to its own file migration-stats.[ch] Juan Quintela
2023-05-03 9:26 ` [PULL 3/8] migration: Rename ram_counters to mig_stats Juan Quintela
2023-05-03 9:26 ` Juan Quintela [this message]
2023-05-03 9:26 ` [PULL 5/8] migration/rdma: Split the zero page case from acct_update_position Juan Quintela
2023-05-03 9:26 ` [PULL 6/8] migration/rdma: Unfold last user of acct_update_position() Juan Quintela
2023-05-03 9:26 ` [PULL 7/8] migration: Drop unused parameter for migration_tls_get_creds() Juan Quintela
2023-05-03 9:26 ` [PULL 8/8] migration: Drop unused parameter for migration_tls_client_create() Juan Quintela
2023-05-03 14:57 ` [PULL 0/8] Migration 20230428 patches Richard Henderson
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=20230503092606.9415-5-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=leobras@redhat.com \
--cc=lukasstraub2@web.de \
--cc=peterx@redhat.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).