From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: [PATCH v5 0/2] Migration: Make more ram_counters atomic
Date: Wed, 26 Apr 2023 22:10:00 +0200 [thread overview]
Message-ID: <20230426201002.15414-1-quintela@redhat.com> (raw)
Hi
In this v5:
Not only change the type of the counters, also use the __nocheck()
variants of the functions.
Please, review.
[v4]
- Change aligned_uint64_t to size_t to make (some) 32bit hosts happy.
Please review.
[v3]
- Addressed reviews
- All counters are now atomic, either Stat64 or atomic.
- Rename duplicated to zero_pages
- Rename normal to zero_pages.
Please review.
[v2]
- fix typos found by David Edmondson
- Add review-by tags.
Please review.
[v1]
On previous series we cerate ram_atomic_counters. But we basically
need that all counters are atomic. So move back to only have
ram_counters, just with a new type that allows the atomic counters.
Once there, move update of stats out of RAM mutex.
And make multifd_bytes atomic.
Later, Juan.
Juan Quintela (2):
migration: Make dirty_pages_rate atomic
migration: Make dirty_bytes_last_sync atomic
migration/migration.c | 9 ++++++---
migration/ram.c | 7 ++++---
migration/ram.h | 4 ++--
3 files changed, 12 insertions(+), 8 deletions(-)
--
2.40.0
next reply other threads:[~2023-04-26 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 20:10 Juan Quintela [this message]
2023-04-26 20:10 ` [PATCH v5 1/2] migration: Make dirty_pages_rate atomic Juan Quintela
2023-04-27 8:17 ` Paolo Bonzini
2023-04-26 20:10 ` [PATCH v5 2/2] migration: Make dirty_bytes_last_sync atomic Juan Quintela
2023-04-27 8:19 ` Paolo Bonzini
2023-04-27 8:40 ` Juan Quintela
2023-04-27 8:41 ` [PATCH v5 0/2] Migration: Make more ram_counters atomic Juan Quintela
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=20230426201002.15414-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).