On 30 June 2014 11:57, Gerd Hoffmann <kra...@redhat.com> wrote: > IIRC "wait for client to connect" is a blocking accept() call. Which > you certainly don't want do in a qmp command handler. So if we switch > over chardevs created via -chardev to use the qmp init code path too we > need some hackery to make '-chardev socket,wait,...' work without > introducing a blocking qmp command I suspect ...
We already have blocking code paths in qmp_chardev_open_socket(): for the non-listening case we call socket_connect() with a NULL callback argument, which will result in our calling connect() in blocking mode. thanks -- PMM
