On Tue, Jan 10, 2023 at 12:45 PM John Snow <js...@redhat.com> wrote:
>
> On Tue, Jan 10, 2023 at 2:05 AM Marc-André Lureau
> <marcandre.lur...@gmail.com> wrote:
> >
> > Hi John
> >
> > On Tue, Jan 10, 2023 at 1:06 AM John Snow <js...@redhat.com> wrote:
> > >
> > > On Mon, Jul 25, 2022 at 7:23 AM Marc-André Lureau
> > > <marcandre.lur...@gmail.com> wrote:
> > > >
> > > > Hi
> > > >
> > > > On Fri, Jul 1, 2022 at 2:51 AM John Snow <js...@redhat.com> wrote:
> > > >>
> > > >> On Thu, Jun 30, 2022 at 8:34 AM <marcandre.lur...@redhat.com> wrote:
> > > >> >
> > > >> > From: Marc-André Lureau <marcandre.lur...@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.
> > > >
> > >
> > > Fair enough - can I kindly ask you to resend, though? My apologies and
> > > Happy New Year!
> >
> > I am confused, what's the relation between QEMU python/qemu/qmp and
> > https://gitlab.com/qemu-project/python-qemu-qmp ?
> >
> > When / how is the code sync ?
> >
>
> python-qemu-qmp supersedes the code that is in qemu.git.
> qemu.git/python/qemu/qmp is scheduled to be deleted, but there are
> changes that need to go in to configure etc to support the deletion
> first, and I've been backlogged/waylaid on making those changes.
... by which I mean, I generally do review and merge on the standalone
repo first, then backport to qemu.git. Or, that's what I'd prefer to
do, since the tooling and testing is more advanced on the standalone
repo.
