All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, lvivier@redhat.com, dgilbert@redhat.com,
	peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/2] migration: Create tcp_port parameter
Date: Thu, 04 Jan 2018 19:16:17 +0100	[thread overview]
Message-ID: <87r2r5a3ri.fsf@secure.laptop> (raw)
In-Reply-To: <3e95592d-4846-bb91-961d-03ca10e3ae18@redhat.com> (Eric Blake's message of "Fri, 1 Dec 2017 12:28:20 -0600")

Eric Blake <eblake@redhat.com> wrote:
> On 12/01/2017 06:57 AM, Juan Quintela wrote:
>> It will be used to store the uri tcp_port parameter.  This is the only
>> parameter than can change and we can need to be able to connect to it.
>>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>>
>> --
>>
>
>> @@ -2422,6 +2430,8 @@ static Property migration_properties[] = {
>>       DEFINE_PROP_SIZE("xbzrle-cache-size", MigrationState,
>>                         parameters.xbzrle_cache_size,
>>                         DEFAULT_MIGRATE_XBZRLE_CACHE_SIZE),
>> +    DEFINE_PROP_UINT16("x-tcp-port", MigrationState,
>> +                       parameters.tcp_port, 0),
>
> Why is this one experimental when others are not,

changing.

Actually, because I don't know if everybody wants this.

>
>>         /* Migration capabilities */
>>       DEFINE_PROP_MIG_CAP("x-xbzrle", MIGRATION_CAPABILITY_XBZRLE),
>> diff --git a/qapi/migration.json b/qapi/migration.json
>> index 4cd3d13158..e2a1d86216 100644
>> --- a/qapi/migration.json
>> +++ b/qapi/migration.json
>> @@ -488,6 +488,9 @@
>>   #                     and a power of 2
>>   #                     (Since 2.11)
>>   #
>> +# @tcp-port: Only used for tcp, to know what is the real port
>
> s/what is the real port/what the real port is/

Changed.

>> +#                     (Since 2.12)
>> +#
>
> Especially since it is not experimental here?
>
>> @@ -564,6 +567,10 @@
>>   #                     needs to be a multiple of the target page size
>>   #                     and a power of 2
>>   #                     (Since 2.11)
>> +#
>> +# @tcp-port: Only used for tcp, to know what is the real port
>
> same wording tweak

Changed..

>> +#                     (Since 2.12)
>> +#
>>   # Since: 2.4
>>   ##
>>   # TODO either fuse back into MigrationParameters, or make
>> @@ -582,7 +589,8 @@
>>               '*block-incremental': 'bool',
>>               '*x-multifd-channels': 'int',
>>               '*x-multifd-page-count': 'int',
>> -            '*xbzrle-cache-size': 'size' } }
>> +            '*xbzrle-cache-size': 'size' ,
>
> the space before comma looks unusual (although it's harmless)


Changed.

Thanks.

>> +            '*tcp-port': 'uint16'} }

  reply	other threads:[~2018-01-04 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 12:57 [Qemu-devel] [PATCH v3 0/2] Improve info migrate output on destination Juan Quintela
2017-12-01 12:57 ` [Qemu-devel] [PATCH v3 1/2] migration: Create tcp_port parameter Juan Quintela
2017-12-01 18:28   ` Eric Blake
2018-01-04 18:16     ` Juan Quintela [this message]
2017-12-05  8:02   ` Peter Xu
2017-12-08 11:53     ` Dr. David Alan Gilbert
2018-01-04 18:18     ` Juan Quintela
2017-12-01 12:57 ` [Qemu-devel] [PATCH v3 2/2] migration: Set the migration tcp port 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=87r2r5a3ri.fsf@secure.laptop \
    --to=quintela@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@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 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.