From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] multifd: Be consistente about using uint64_t
Date: Fri, 17 Jan 2020 14:56:54 +0000 [thread overview]
Message-ID: <20200117145654.GH3209@work-vm> (raw)
In-Reply-To: <20200117135639.14602-1-quintela@redhat.com>
* Juan Quintela (quintela@redhat.com) wrote:
> We transmit ram_addr_t always as uint64_t. Be consistent in its
> use (on 64bit system, it is always uint64_t problem is 32bits).
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
(Note typo in subject )
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/ram.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/migration/ram.c b/migration/ram.c
> index 96feb4062c..f7482b1b35 100644
> --- a/migration/ram.c
> +++ b/migration/ram.c
> @@ -803,7 +803,10 @@ static void multifd_send_fill_packet(MultiFDSendParams *p)
> }
>
> for (i = 0; i < p->pages->used; i++) {
> - packet->offset[i] = cpu_to_be64(p->pages->offset[i]);
> + /* there are architectures where ram_addr_t is 32 bit */
> + uint64_t temp = p->pages->offset[i];
> +
> + packet->offset[i] = cpu_to_be64(temp);
> }
> }
>
> @@ -877,10 +880,10 @@ static int multifd_recv_unfill_packet(MultiFDRecvParams *p, Error **errp)
> }
>
> for (i = 0; i < p->pages->used; i++) {
> - ram_addr_t offset = be64_to_cpu(packet->offset[i]);
> + uint64_t offset = be64_to_cpu(packet->offset[i]);
>
> if (offset > (block->used_length - TARGET_PAGE_SIZE)) {
> - error_setg(errp, "multifd: offset too long " RAM_ADDR_FMT
> + error_setg(errp, "multifd: offset too long %" PRId64
> " (max " RAM_ADDR_FMT ")",
> offset, block->max_length);
> return -1;
> @@ -1236,7 +1239,7 @@ int multifd_save_setup(void)
> p->id = i;
> p->pages = multifd_pages_init(page_count);
> p->packet_len = sizeof(MultiFDPacket_t)
> - + sizeof(ram_addr_t) * page_count;
> + + sizeof(uint64_t) * page_count;
> p->packet = g_malloc0(p->packet_len);
> p->packet->magic = cpu_to_be32(MULTIFD_MAGIC);
> p->packet->version = cpu_to_be32(MULTIFD_VERSION);
> @@ -1447,7 +1450,7 @@ int multifd_load_setup(void)
> p->id = i;
> p->pages = multifd_pages_init(page_count);
> p->packet_len = sizeof(MultiFDPacket_t)
> - + sizeof(ram_addr_t) * page_count;
> + + sizeof(uint64_t) * page_count;
> p->packet = g_malloc0(p->packet_len);
> p->name = g_strdup_printf("multifdrecv_%d", i);
> }
> --
> 2.24.1
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2020-01-17 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 13:56 [PATCH] multifd: Be consistente about using uint64_t Juan Quintela
2020-01-17 14:03 ` Philippe Mathieu-Daudé
2020-01-17 14:56 ` Dr. David Alan Gilbert [this message]
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=20200117145654.GH3209@work-vm \
--to=dgilbert@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.