qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
	lvivier@redhat.com, qemu-devel@nongnu.org, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH v7 4/8] migration: Create socket-address parameter
Date: Fri, 13 Apr 2018 13:02:34 +0100	[thread overview]
Message-ID: <20180413120234.GF16263@redhat.com> (raw)
In-Reply-To: <20180412130932.GG2704@work-vm>

On Thu, Apr 12, 2018 at 02:09:33PM +0100, Dr. David Alan Gilbert wrote:
> * Juan Quintela (quintela@redhat.com) 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>
> > 
> > --
> > 
> > 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.
> 
> Is there a reason it's a parameter rather than just an entry in
> MigrationInfo?

I imagine it is a side-effect of earlier versions of this patch
which used the migration parameter setter method. Having it in
the MigrationInfo does seem reasonable to me since this is not
a tunable parameter.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2018-04-13 12:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 11:27 [Qemu-devel] [PATCH v7 0/8] Add make check tests for Migration Juan Quintela
2018-04-04 11:27 ` [Qemu-devel] [PATCH v7 1/8] qemu-sockets: Export SocketAddress_to_str Juan Quintela
2018-04-13 11:54   ` Daniel P. Berrangé
2018-05-08  7:49     ` Juan Quintela
2018-04-04 11:27 ` [Qemu-devel] [PATCH v7 2/8] tests: Add migration precopy test Juan Quintela
2018-04-04 11:27 ` [Qemu-devel] [PATCH v7 3/8] tests: Add migration xbzrle test Juan Quintela
2018-04-04 11:27 ` [Qemu-devel] [PATCH v7 4/8] migration: Create socket-address parameter Juan Quintela
2018-04-12 13:09   ` Dr. David Alan Gilbert
2018-04-13 12:02     ` Daniel P. Berrangé [this message]
2018-05-08  7:51       ` Juan Quintela
2018-05-08  7:50     ` Juan Quintela
2018-04-13 12:01   ` Daniel P. Berrangé
2018-05-08  8:02     ` Juan Quintela
2018-04-04 11:27 ` [Qemu-devel] [PATCH v7 5/8] tests: Migration ppc now inlines its program Juan Quintela
2018-04-04 11:27 ` [Qemu-devel] [PATCH v7 6/8] tests: Add basic migration precopy tcp test Juan Quintela
2018-04-04 11:27 ` [Qemu-devel] [PATCH v7 7/8] migration: Add multifd test Juan Quintela
2018-04-04 11:27 ` [Qemu-devel] [PATCH v7 8/8] [RFH] tests: Add migration compress threads tests 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=20180413120234.GF16263@redhat.com \
    --to=berrange@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).