qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, mdroth@linux.vnet.ibm.com, alevy@redhat.com,
	kraxel@redhat.com, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] QAPI conversion status and async commands support
Date: Wed, 7 Mar 2012 13:36:44 -0300	[thread overview]
Message-ID: <20120307133644.63d2e662@doriath.home> (raw)

Hi there,

In the last few weeks we've had some proposals for new QMP commands that need
to be asynchronous. As we lack a standard asynchronous API today, each command
ends up adding its own way to execute in the background.

This multiplies the API complexity as each command has to be implemented and
learned by clients separately, with their own way of doing more or less the
same things.

The solution for this, envisioned for us for a long time now, is to introduce
an unified QMP API for asynchronous commands.

But before doing this we have to:

  1. Finish the commands conversion to the QAPI

     This is almost done, the only missing commands are: add_graphics_client,
     do_closefd, do_device_add, do_device_del, do_getfd, do_migrate,
     do_netdev_add, do_netdev_del, do_qmp_capabilities and do_screen_dump.

     Note that do_migrate has already been posted to the list, and I have
     the screendump more or less done. Also, Anthony has an old branch where most
     of the conversions are already done, they just need to be rebased & tested.

  2. Integrate the new QAPI server

     Implemented by Anthony, may have missing pieces.

  3. Implement async command support


I think the missing commands to be converted can be done in around one week,
but unfortunately I've been busy at other things and will need a few days to
resume this work. Then there's the new QAPI server & async support, which I'm
not sure how much time we'll need to integrate them, but we should have this
done for 1.1.

The main question is: what should we do for the already posted async commands?
Should we hold them until we finish this work?

             reply	other threads:[~2012-03-07 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 16:36 Luiz Capitulino [this message]
2012-03-07 17:29 ` [Qemu-devel] QAPI conversion status and async commands support Paolo Bonzini
2012-03-07 17:36   ` Anthony Liguori
2012-03-07 18:12     ` Luiz Capitulino
2012-03-12  8:43       ` Wen Congyang
2012-03-12 13:50         ` Luiz Capitulino
2012-03-07 20:06     ` Alon Levy
2012-03-12  7:30       ` Alon Levy
2012-03-08 12:34     ` Kevin Wolf
2012-03-08 14:12       ` Paolo Bonzini
2012-03-08 14:22         ` Kevin Wolf

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=20120307133644.63d2e662@doriath.home \
    --to=lcapitulino@redhat.com \
    --cc=alevy@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.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).