[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 14/15] chardev: tcp: postpone async connectio
From: |
Daniel P . Berrangé |
Subject: |
Re: [Qemu-devel] [PATCH v2 14/15] chardev: tcp: postpone async connection setup |
Date: |
Thu, 1 Mar 2018 16:01:38 +0000 |
User-agent: |
Mutt/1.9.2 (2017-12-15) |
On Thu, Mar 01, 2018 at 04:44:37PM +0800, Peter Xu wrote:
> This patch allows the socket chardev async connection be setup with
> non-default gcontext. We do it by postponing the setup to machine done,
> since until then we can know which context we should run the async
> operation on.
>
> Signed-off-by: Peter Xu <address@hidden>
> ---
> chardev/char-socket.c | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
I don't like this as it is special casing behaviour wrt GMainContext
only the the case where the chardev is configured as a client with
non-blocking connect. So any code that uses chardevs and wants to
set a different GMainContext may or may not work, depending on
whether the user gave the ',wait' option to the chardev. I'm struggling
to see why this is really needed at all.
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 :|
- [Qemu-devel] [PATCH v2 11/15] qio: non-default context for TLS handshake, (continued)
- [Qemu-devel] [PATCH v2 11/15] qio: non-default context for TLS handshake, Peter Xu, 2018/03/01
- [Qemu-devel] [PATCH v2 12/15] chardev: introduce chr_machine_done hook, Peter Xu, 2018/03/01
- [Qemu-devel] [PATCH v2 13/15] char: use chardev's gcontext for async connect, Peter Xu, 2018/03/01
- [Qemu-devel] [PATCH v2 14/15] chardev: tcp: postpone async connection setup, Peter Xu, 2018/03/01
- [Qemu-devel] [PATCH v2 15/15] chardev: tcp: postpone TLS work until machine done, Peter Xu, 2018/03/01
- Re: [Qemu-devel] [PATCH v2 00/15] qio: general non-default GMainContext support, Daniel P . Berrangé, 2018/03/01