qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Edmondson <david.edmondson@oracle.com>
To: Juan Quintela <quintela@redhat.com>
Cc: "Eduardo Habkost" <eduardo@habkost.net>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	qemu-devel@nongnu.org, "Yanan Wang" <wangyanan55@huawei.com>,
	"Leonardo Bras" <leobras@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH v5 1/8] migration: Export ram_transferred_ram()
Date: Tue, 29 Mar 2022 12:48:20 +0100	[thread overview]
Message-ID: <cunpmm5f08r.fsf@oracle.com> (raw)
In-Reply-To: <20220310153454.3929-2-quintela@redhat.com> (Juan Quintela's message of "Thu, 10 Mar 2022 16:34:47 +0100")

On Thursday, 2022-03-10 at 16:34:47 +01, Juan Quintela wrote:

> Subject: Re: [PATCH v5 1/8] migration: Export ram_transferred_ram()

The function is "ram_transferred_add()".

> Signed-off-by: Juan Quintela <quintela@redhat.com>

Reviewed-by: David Edmondson <david.edmondson@oracle.com>

> ---
>  migration/ram.h | 2 ++
>  migration/ram.c | 2 +-
>  2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/migration/ram.h b/migration/ram.h
> index 2c6dc3675d..2e27c49f90 100644
> --- a/migration/ram.h
> +++ b/migration/ram.h
> @@ -64,6 +64,8 @@ int ram_postcopy_incoming_init(MigrationIncomingState *mis);
>
>  void ram_handle_compressed(void *host, uint8_t ch, uint64_t size);
>
> +void ram_transferred_add(uint64_t bytes);
> +
>  int ramblock_recv_bitmap_test(RAMBlock *rb, void *host_addr);
>  bool ramblock_recv_bitmap_test_byte_offset(RAMBlock *rb, uint64_t byte_offset);
>  void ramblock_recv_bitmap_set(RAMBlock *rb, void *host_addr);
> diff --git a/migration/ram.c b/migration/ram.c
> index 170e522a1f..947ed44c89 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -394,7 +394,7 @@ uint64_t ram_bytes_remaining(void)
>
>  MigrationStats ram_counters;
>
> -static void ram_transferred_add(uint64_t bytes)
> +void ram_transferred_add(uint64_t bytes)
>  {
>      if (runstate_is_running()) {
>          ram_counters.precopy_bytes += bytes;

dme.
-- 
Oh well, I'm dressed up so nice and I'm doing my best.


  parent reply	other threads:[~2022-03-29 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 15:34 [PATCH v5 0/8] Migration: Transmit and detect zero pages in the multifd threads Juan Quintela
2022-03-10 15:34 ` [PATCH v5 1/8] migration: Export ram_transferred_ram() Juan Quintela
2022-03-21 11:50   ` Dr. David Alan Gilbert
2022-03-29 11:48   ` David Edmondson [this message]
2022-03-10 15:34 ` [PATCH v5 2/8] multifd: Count the number of sent bytes correctly Juan Quintela
2022-03-10 15:34 ` [PATCH v5 3/8] migration: Make ram_save_target_page() a pointer Juan Quintela
2022-03-10 15:34 ` [PATCH v5 4/8] multifd: Add property to enable/disable zero_page Juan Quintela
2022-03-10 15:34 ` [PATCH v5 5/8] migration: Export ram_release_page() Juan Quintela
2022-03-10 15:34 ` [PATCH v5 6/8] multifd: Support for zero pages transmission Juan Quintela
2022-03-10 15:34 ` [PATCH v5 7/8] multifd: Zero " Juan Quintela
2022-03-10 15:34 ` [PATCH v5 8/8] migration: Use multifd before we check for the zero page 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=cunpmm5f08r.fsf@oracle.com \
    --to=david.edmondson@oracle.com \
    --cc=dgilbert@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=f4bug@amsat.org \
    --cc=leobras@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=wangyanan55@huawei.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).