From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: John Snow <jsnow@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
Cleber Rosa <crosa@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Beraldo Leal <bleal@redhat.com>
Subject: Re: [PATCH v2 0/3] python/qemu/machine: fix potential hang in QMP accept
Date: Mon, 25 Jul 2022 12:27:48 +0100 [thread overview]
Message-ID: <Yt5+NMuW+l4OhDH2@redhat.com> (raw)
In-Reply-To: <CAJ+F1C+NEqp-P9BAzT5ADkxVP_pZyvtZPAOVz3R_Xq0w7tCmpg@mail.gmail.com>
On Mon, Jul 25, 2022 at 03:23:26PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Fri, Jul 1, 2022 at 2:51 AM John Snow <jsnow@redhat.com> wrote:
>
> > On Thu, Jun 30, 2022 at 8:34 AM <marcandre.lureau@redhat.com> wrote:
> > >
> > > From: Marc-André Lureau <marcandre.lureau@redhat.com>
> > >
> > > Hi,
> > >
> > > As reported earlier by Richard Henderson ("virgl avocado hang" thread),
> > avocado
> > > tests may hang when QEMU exits before the QMP connection is established.
> > >
> > > v2:
> > > - use a socketpair() for QMP (instead of async concurrent code from v1)
> > as
> > > suggested by Daniel Berrange.
> > > - should not regress (hopefully)
> > >
> > > Marc-André Lureau (3):
> > > python/qmp/protocol: add open_with_socket()
> > > python/qmp/legacy: make QEMUMonitorProtocol accept a socket
> > > python/qemu/machine: use socketpair() for QMP by default
> > >
> > > python/qemu/machine/machine.py | 24 ++++++++++++++++--------
> > > python/qemu/qmp/legacy.py | 18 +++++++++++++++---
> > > python/qemu/qmp/protocol.py | 25 ++++++++++++++++++++-----
> > > 3 files changed, 51 insertions(+), 16 deletions(-)
> > >
> > > --
> > > 2.37.0.rc0
> > >
> >
> > For anything that touches python/qemu/qmp/*, may I please ask that you
> > submit them to https://gitlab.com/qemu-project/python-qemu-qmp ?
> >
> >
> Ok
>
>
> > (I'll review them in the meantime on-list just in the interest of
> > moving things along.)
> >
>
> I was waiting for a review before updating the patches / moving to
> python-qemu-qmp.
This code looks decent to me
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With 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:[~2022-07-25 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 12:34 [PATCH v2 0/3] python/qemu/machine: fix potential hang in QMP accept marcandre.lureau
2022-06-30 12:34 ` [PATCH v2 1/3] python/qmp/protocol: add open_with_socket() marcandre.lureau
2022-06-30 12:34 ` [PATCH v2 2/3] python/qmp/legacy: make QEMUMonitorProtocol accept a socket marcandre.lureau
2022-06-30 12:34 ` [PATCH v2 3/3] python/qemu/machine: use socketpair() for QMP by default marcandre.lureau
2022-07-25 11:29 ` Daniel P. Berrangé
2022-06-30 22:49 ` [PATCH v2 0/3] python/qemu/machine: fix potential hang in QMP accept John Snow
2022-07-25 11:23 ` Marc-André Lureau
2022-07-25 11:27 ` Daniel P. Berrangé [this message]
2023-01-09 21:06 ` John Snow
2023-01-10 7:05 ` Marc-André Lureau
2023-01-10 17:45 ` John Snow
2023-01-11 19:44 ` John Snow
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=Yt5+NMuW+l4OhDH2@redhat.com \
--to=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).