From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: David Edmondson <david.edmondson@oracle.com>, qemu-devel@nongnu.org
Cc: Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [RFC v2 1/2] migration: Introduce ram_transferred_add()
Date: Tue, 21 Dec 2021 09:37:01 +0100 [thread overview]
Message-ID: <3a5ead42-0dbb-2dd0-7a71-9daa9e1aaa80@redhat.com> (raw)
In-Reply-To: <20211220093413.1383190-2-david.edmondson@oracle.com>
On 12/20/21 10:34, David Edmondson wrote:
> ...and use it.
FYI Not all mails readers / git tools display subject along
with content, so it is more helpful to rewrite the subject.
> Signed-off-by: David Edmondson <david.edmondson@oracle.com>
> ---
> migration/ram.c | 23 ++++++++++++++---------
> 1 file changed, 14 insertions(+), 9 deletions(-)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 57efa67f20..bd53e50a7f 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -386,6 +386,11 @@ uint64_t ram_bytes_remaining(void)
>
> MigrationStats ram_counters;
>
> +static void ram_transferred_add(uint64_t bytes)
> +{
> + ram_counters.transferred += bytes;
> +}
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2021-12-21 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 9:34 [RFC v2 0/2] migration: Tally pre-copy, downtime and post-copy bytes independently David Edmondson
2021-12-20 9:34 ` [RFC v2 1/2] migration: Introduce ram_transferred_add() David Edmondson
2021-12-21 8:37 ` Philippe Mathieu-Daudé [this message]
2021-12-20 9:34 ` [RFC v2 2/2] migration: Tally pre-copy, downtime and post-copy bytes independently David Edmondson
2021-12-21 8:28 ` Philippe Mathieu-Daudé
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=3a5ead42-0dbb-2dd0-7a71-9daa9e1aaa80@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=dgilbert@redhat.com \
--cc=eblake@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).