qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: lvivier@redhat.com, dgilbert@redhat.com, peterx@redhat.com,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v10 2/5] migration: Create socket-address parameter
Date: Wed, 28 Nov 2018 08:27:40 -0600	[thread overview]
Message-ID: <743778f1-1769-502d-26ff-51c17578e283@redhat.com> (raw)
In-Reply-To: <20181128113337.7238-3-quintela@redhat.com>

On 11/28/18 5:33 AM, Juan Quintela wrote:
> It will be used to store the uri parameters. We want this only for
> tcp, so we don't set it for other uris.  We need it to know what port
> is migration running.
> 
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> 
> --
> 

That's not the typical --- separator that git-am would recognize.

> This used to be uri parameter, but it has so many troubles to
> reproduce that it don't just make sense.
> 
> This used to be a port parameter.  I was asked to move to
> SocketAddress, done.
> I also merged the setting of the migration tcp port in this one
> because now I need to free the address, and this makes it easier.
> This used to be x-socket-address with a single direction, now it is a
> list of addresses.
> Move SocketAddress_to_str here.  I used to try to generalize the one
> in chardev/char-socket.c, but it is not worth it.
> 
> Signed-off-by: Juan Quintela <quintela@redhat.com>

the double S-o-b is odd, especially if the second one was intended to be 
stripped.


> +++ b/qapi/migration.json
> @@ -6,6 +6,7 @@
>   ##
>   
>   { 'include': 'common.json' }
> +{ 'include': 'sockets.json' }
>   
>   ##
>   # @MigrationStats:
> @@ -196,6 +197,8 @@
>   # @compression: migration compression statistics, only returned if compression
>   #           feature is on and status is 'active' or 'completed' (Since 3.1)
>   #
> +# @socket-address: Only used for tcp, to know what the real port is (Since 3.1)
> +#

s/3.1/4.0/ now...

> +++ b/qapi/sockets.json
> @@ -152,3 +152,16 @@
>               'unix': 'UnixSocketAddress',
>               'vsock': 'VsockSocketAddress',
>               'fd': 'String' } }
> +
> +##
> +# @DummyStruct:
> +#
> +# Both block-core and migration needs SocketAddressList
> +# I am open to comments about how to share it
> +#
> +# @dummy-list: A dummy list
> +#
> +# Since: 3.1
> +##
> +{ 'struct': 'DummyStruct',
> +  'data': { 'dummy-list': ['SocketAddress'] } }

We've had a couple of threads about this in the last couple of months; 
maybe it's time for a qapi generator patch where we add an optional 
'gen-list':true marker to any struct that needs to have a list generated 
for C code even when no QMP command uses the list form.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-11-28 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 11:33 [Qemu-devel] [PATCH v10 0/5] Add make check tests for Migration Juan Quintela
2018-11-28 11:33 ` [Qemu-devel] [PATCH v10 1/5] tests: Add migration xbzrle test Juan Quintela
2018-11-28 11:33 ` [Qemu-devel] [PATCH v10 2/5] migration: Create socket-address parameter Juan Quintela
2018-11-28 14:27   ` Eric Blake [this message]
2018-11-29  9:30     ` Markus Armbruster
2018-11-28 11:33 ` [Qemu-devel] [PATCH v10 3/5] tests: Add basic migration precopy tcp test Juan Quintela
2018-11-28 11:33 ` [Qemu-devel] [PATCH v10 4/5] tests: Add migration multifd test Juan Quintela
2018-11-28 11:33 ` [Qemu-devel] [PATCH v10 5/5] [RFH] tests: Add migration compress threads tests Juan Quintela
2018-11-29 10:23 ` [Qemu-devel] [PATCH v10 0/5] Add make check tests for Migration Daniel P. Berrangé

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=743778f1-1769-502d-26ff-51c17578e283@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peterx@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).