From: Juan Quintela <quintela@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/2] migration: Create tcp_port parameter
Date: Thu, 04 Jan 2018 19:18:15 +0100 [thread overview]
Message-ID: <87mv1ta3o8.fsf@secure.laptop> (raw)
In-Reply-To: <20171205080230.GD2925@xz-mi> (Peter Xu's message of "Tue, 5 Dec 2017 16:02:30 +0800")
Peter Xu <peterx@redhat.com> wrote:
>> @@ -1659,6 +1662,10 @@ void hmp_migrate_set_parameter(Monitor *mon, const QDict *qdict)
>> }
>> p->xbzrle_cache_size = cache_size;
>> break;
>> + case MIGRATION_PARAMETER_TCP_PORT:
>> + p->has_tcp_port = true;
>> + visit_type_uint16(v, param, &p->tcp_port, &err);
>
> Should we allow user to set this parameter? Or it's just used for
> query, only? (AFAIU from next patch, this is only used for query)
Only for query. Really it is only needed for tcp, due to the wierd way
that ports are allocated to allow for test running in parallel safely.
>
>> + break;
>> default:
>> assert(0);
>> }
>> diff --git a/migration/migration.c b/migration/migration.c
>> index 19917a4b5b..abc02d4efd 100644
>> --- a/migration/migration.c
>> +++ b/migration/migration.c
>> @@ -517,6 +517,8 @@ MigrationParameters *qmp_query_migrate_parameters(Error **errp)
>> params->x_multifd_page_count = s->parameters.x_multifd_page_count;
>> params->has_xbzrle_cache_size = true;
>> params->xbzrle_cache_size = s->parameters.xbzrle_cache_size;
>> + params->has_tcp_port = true;
>> + params->tcp_port = s->parameters.tcp_port;
>>
>> return params;
>> }
>> @@ -884,6 +886,9 @@ static void migrate_params_test_apply(MigrateSetParameters *params,
>> if (params->has_xbzrle_cache_size) {
>> dest->xbzrle_cache_size = params->xbzrle_cache_size;
>> }
>> + if (params->has_tcp_port) {
>> + dest->tcp_port = params->tcp_port;
>> + }
>> }
>>
>> static void migrate_params_apply(MigrateSetParameters *params, Error **errp)
>> @@ -956,6 +961,9 @@ static void migrate_params_apply(MigrateSetParameters *params, Error **errp)
>> s->parameters.xbzrle_cache_size = params->xbzrle_cache_size;
>> xbzrle_cache_resize(params->xbzrle_cache_size, errp);
>> }
>> + if (params->has_tcp_port) {
>> + s->parameters.tcp_port = params->tcp_port;
>> + }
>> }
>>
>> void qmp_migrate_set_parameters(MigrateSetParameters *params, Error **errp)
>> @@ -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),
>
> Same question here... If it's only for querying, why allow user to
> specify it?
You are right.
Because *I* changed the x-uri bits into this. and for x-uri it made
sense.
And I just did the conversion, witohut too much thinking.
Later, Juan.
next prev parent reply other threads:[~2018-01-04 18:18 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
2017-12-05 8:02 ` Peter Xu
2017-12-08 11:53 ` Dr. David Alan Gilbert
2018-01-04 18:18 ` Juan Quintela [this message]
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=87mv1ta3o8.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 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.