On Thu, Jul 12, 2018 at 05:36:00PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("Re: [PATCH v3.1] libxl: Design of an async API to
> issue QMP commands to QEMU"):
> > I don't think the state of a qmp connection can fit into
> > libxl__qmp_cmd_state. The "Active" state doesn't mean that a
Sorry for not noticing that you had replied.
Anthony PERARD writes ("Re: [PATCH v3.1] libxl: Design of an async API to issue
QMP commands to QEMU"):
> Before replying to this email, here is the description of what state a
> QMP connection can be. This states are only internal to libxl_qmp.c, the
On Tue, Jul 03, 2018 at 03:48:22PM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("[PATCH v3.1] libxl: Design of an async API to issue
> QMP commands to QEMU"):
> > All the functions will be implemented in later patches.
>
> Thanks, this really makes things clearer for me.
>
> > What do you
Anthony PERARD writes ("[PATCH v3.1] libxl: Design of an async API to issue QMP
commands to QEMU"):
> All the functions will be implemented in later patches.
Thanks, this really makes things clearer for me.
> What do you think of this design? This is the same as in my patch series
> with new
All the functions will be implemented in later patches.
Signed-off-by: Anthony PERARD
---
What do you think of this design? This is the same as in my patch series
with new names (to avoid confusion with libxl___ev_*) and documentation.
I'll write something as well for the internal of the
