From: Juan Quintela <quintela@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, lvivier@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH v12 08/21] migration: Transmit initial package through the multifd channels
Date: Wed, 09 May 2018 10:34:57 +0200 [thread overview]
Message-ID: <871sel6xce.fsf@secure.laptop> (raw)
In-Reply-To: <20180502171938.GJ2679@work-vm> (David Alan Gilbert's message of "Wed, 2 May 2018 18:19:39 +0100")
"Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
> * Juan Quintela (quintela@redhat.com) wrote:
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>
> Please print the magic with %x.
done.
>
>> + return -1;
>> + }
>> +
>> + if (msg.version != MULTIFD_VERSION) {
>> + error_setg(errp, "multifd: received packet version %d "
>> + "expected %d", msg.version, MULTIFD_VERSION);
>> + return -1;
>> + }
>> +
>> + if (memcmp(msg.uuid, &qemu_uuid, sizeof(qemu_uuid))) {
>> + char *uuid = qemu_uuid_unparse_strdup(&qemu_uuid);
>> + error_setg(errp, "multifd: received uuid '%s' and expected "
>> + "uuid '%s' for channel %hhd", msg.uuid, uuid, msg.id);
>
> I don't think you can just print msg.uuid there; it's the raw 16 bytes
> isn't it rather than a string?
You ae right.
> I suspect you need to do the unprase on both of them.
Done.
Thanks, Juan.
next prev parent reply other threads:[~2018-05-09 8:32 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 11:27 [Qemu-devel] [PATCH v12 00/21] Multifd Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 01/21] migration: Set error state in case of error Juan Quintela
2018-05-02 15:53 ` Dr. David Alan Gilbert
2018-05-09 8:15 ` Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 02/21] migration: Introduce multifd_recv_new_channel() Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 03/21] migration: terminate_* can be called for other threads Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 04/21] migration: Be sure all recv channels are created Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 05/21] migration: Export functions to create send channels Juan Quintela
2018-04-26 7:28 ` Peter Xu
2018-05-09 8:05 ` Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 06/21] migration: Create multifd channels Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 07/21] migration: Delay start of migration main routines Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 08/21] migration: Transmit initial package through the multifd channels Juan Quintela
2018-05-02 17:19 ` Dr. David Alan Gilbert
2018-05-09 8:34 ` Juan Quintela [this message]
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 09/21] migration: Define MultifdRecvParams sooner Juan Quintela
2018-05-02 17:32 ` Dr. David Alan Gilbert
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 10/21] migration: Create multipage support Juan Quintela
2018-04-26 7:15 ` Peter Xu
2018-05-09 10:52 ` Juan Quintela
2018-05-02 17:52 ` Dr. David Alan Gilbert
2018-05-09 10:53 ` Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 11/21] migration: Create multifd packet Juan Quintela
2018-05-02 18:04 ` Dr. David Alan Gilbert
2018-05-09 11:09 ` Juan Quintela
2018-05-09 11:12 ` Dr. David Alan Gilbert
2018-05-09 19:46 ` Juan Quintela
2018-05-11 16:36 ` Dr. David Alan Gilbert
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 12/21] migration: Add multifd traces for start/end thread Juan Quintela
2018-05-02 18:35 ` Dr. David Alan Gilbert
2018-05-09 11:11 ` Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 13/21] migration: Calculate transferred ram correctly Juan Quintela
2018-05-02 18:59 ` Dr. David Alan Gilbert
2018-05-09 11:14 ` Juan Quintela
2018-05-09 19:46 ` Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 14/21] migration: Multifd channels always wait on the sem Juan Quintela
2018-05-03 9:36 ` Dr. David Alan Gilbert
2018-05-23 10:59 ` Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 15/21] migration: Add block where to send/receive packets Juan Quintela
2018-05-03 10:03 ` Dr. David Alan Gilbert
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 16/21] migration: Synchronize multifd threads with main thread Juan Quintela
2018-05-03 10:44 ` Dr. David Alan Gilbert
2018-05-09 19:45 ` Juan Quintela
2018-05-11 16:32 ` Dr. David Alan Gilbert
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 17/21] migration: Create ram_multifd_page Juan Quintela
2018-04-26 7:43 ` Peter Xu
2018-04-26 8:18 ` Peter Xu
2018-05-03 11:30 ` Dr. David Alan Gilbert
2018-05-23 11:13 ` Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 18/21] migration: Start sending messages Juan Quintela
2018-05-03 14:55 ` Dr. David Alan Gilbert
2018-05-23 10:51 ` Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 19/21] migration: Wait for blocking IO Juan Quintela
2018-05-03 15:04 ` Dr. David Alan Gilbert
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 20/21] migration: Remove not needed semaphore and quit Juan Quintela
2018-04-25 11:27 ` [Qemu-devel] [PATCH v12 21/21] migration: Stop sending whole pages through main channel Juan Quintela
2018-05-03 15:24 ` Dr. David Alan Gilbert
2018-04-25 11:44 ` [Qemu-devel] [PATCH v12 00/21] Multifd Juan Quintela
2018-05-03 15:32 ` Dr. David Alan Gilbert
2018-04-26 8:28 ` Peter Xu
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=871sel6xce.fsf@secure.laptop \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--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).