From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.12 REPOST] migration: convert socket server to QIONetListener
Date: Tue, 13 Mar 2018 11:06:52 +0000 [thread overview]
Message-ID: <20180313110652.GS3048@redhat.com> (raw)
In-Reply-To: <be16f4e2-7b97-e251-332e-9445e4d9965c@redhat.com>
On Tue, Mar 13, 2018 at 11:57:17AM +0100, Paolo Bonzini wrote:
> On 13/03/2018 10:20, Dr. David Alan Gilbert wrote:
> >> static void socket_start_incoming_migration(SocketAddress *saddr,
> >> Error **errp)
> >> {
> >> - QIOChannelSocket *listen_ioc = qio_channel_socket_new();
> >> + QIONetListener *listener = qio_net_listener_new();
> >>
> >> - qio_channel_set_name(QIO_CHANNEL(listen_ioc),
> >> - "migration-socket-listener");
> >> + qio_net_listener_set_name(listener, "migration-socket-listener");
> >>
> >> - if (qio_channel_socket_listen_sync(listen_ioc, saddr, errp) < 0) {
> >> - object_unref(OBJECT(listen_ioc));
> >> + if (qio_net_listener_open_sync(listener, saddr, errp) < 0) {
> >> + object_unref(OBJECT(listener));
> >> return;
> >> }
> >>
> >> - qio_channel_add_watch(QIO_CHANNEL(listen_ioc),
> >> - G_IO_IN,
> >> - socket_accept_incoming_migration,
> >> - listen_ioc,
> >> - (GDestroyNotify)object_unref);
> >> + qio_net_listener_set_client_func(listener,
> >> + socket_accept_incoming_migration,
> >> + NULL, NULL);
> >> }
> >>
> >> void tcp_start_incoming_migration(const char *host_port, Error **errp)
> >> --
> >> 2.14.3
> >>
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >
>
> Could this get in 2.12 as a bugfix, even after soft freeze? It's the
> last user of qio_channel_listen_sync that blocks full IPv4/IPv6 support.
> All other users are for vsock/AF_UNIX.
I had been thinking of all this conversion as feature, but I guess if we
squint our eyes a bit we could claim it is just a bugfix on the grounds
that it is fixing broken IPv4/6 dual stack support.
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 :|
next prev parent reply other threads:[~2018-03-13 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 14:17 [Qemu-devel] [PATCH for-2.12 REPOST] migration: convert socket server to QIONetListener Daniel P. Berrangé
2018-03-13 9:20 ` Dr. David Alan Gilbert
2018-03-13 10:57 ` Paolo Bonzini
2018-03-13 11:06 ` Daniel P. Berrangé [this message]
2018-03-13 11:19 ` Paolo Bonzini
2018-03-13 11:24 ` Dr. David Alan Gilbert
2018-03-23 16:27 ` Dr. David Alan Gilbert
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=20180313110652.GS3048@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@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 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.