qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] ANN: QEMU Monitor Protocol git tree
Date: Wed, 23 Sep 2009 11:21:29 -0300	[thread overview]
Message-ID: <20090923112129.4c3bff63@doriath> (raw)
In-Reply-To: <20090923100822.GF29269@redhat.com>

On Wed, 23 Sep 2009 11:08:22 +0100
"Daniel P. Berrange" <berrange@redhat.com> wrote:

> On Mon, Sep 21, 2009 at 10:44:30PM -0300, Luiz Capitulino wrote:
> > 
> >  Hi there,
> > 
> > While I was converting command handlers to the QObject style I realized that
> > it would be very interesting to have the protocol working up front, so that
> > converted handlers could be tested to assure that their data types have been
> > chosen correctly.
> > 
> > More importantly, some protocol design decisions can affect handlers signatures,
> > so having at least an idea of how the protocol will look like will help us to
> > stay on the right track during mass conversion.
> > 
> > So, I have implemented a rudimentary version of the QEMU Monitor Protocol (QMP)
> > it has a command-line switch to enable the protocol.
> > 
> > You will find it at:
> > 
> > http://repo.or.cz/w/qemu/qmp-unstable.git
> > 
> > The QMP directory of that tree has some documents plus a Python script which
> > communicates with QEMU by using the protocol and emulates a shell, although
> > only few commands are working..
> 
> It doesn't compile on i386
> 
> $ make
>   CC    i386-softmmu/monitor.o
> cc1: warnings being treated as errors
> /home/berrange/src/external/qmp-unstable/monitor.c: In function ‘monitor_json_emitter’:
> /home/berrange/src/external/qmp-unstable/monitor.c:277: error: format ‘%li’ expects type ‘long int’, but argument 3 has type ‘int64_t’
> /home/berrange/src/external/qmp-unstable/monitor.c: In function ‘monitor_print_qobject’:
> /home/berrange/src/external/qmp-unstable/monitor.c:398: error: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int64_t’
> make[1]: *** [monitor.o] Error 1

 Fixed.

 Note that I'm rebasing this tree, so that I can cherry-pick
patches easily for upstream submission.

  reply	other threads:[~2009-09-23 14:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22  1:44 [Qemu-devel] ANN: QEMU Monitor Protocol git tree Luiz Capitulino
2009-09-23  1:56 ` Anthony Liguori
2009-09-23  9:57   ` Daniel P. Berrange
2009-09-23 10:57     ` Avi Kivity
2009-09-23 13:40       ` [Qemu-devel] " Paolo Bonzini
2009-09-23 14:04         ` Avi Kivity
2009-09-23 15:19           ` Nathan Baum
2009-09-23 15:40             ` Luiz Capitulino
2009-09-23 18:15           ` Anthony Liguori
2009-09-23 18:36             ` Jamie Lokier
2009-09-23 18:45               ` Paolo Bonzini
2009-09-23 16:01     ` [Qemu-devel] " Markus Armbruster
2009-09-23 16:11       ` Luiz Capitulino
2009-09-23 18:15         ` Jamie Lokier
2009-09-23 18:18       ` Anthony Liguori
2009-09-23 17:08     ` Daniel P. Berrange
2009-09-23 19:07       ` Luiz Capitulino
2009-09-23 14:18   ` Luiz Capitulino
2009-09-23 18:21     ` Anthony Liguori
2009-09-23 10:08 ` Daniel P. Berrange
2009-09-23 14:21   ` Luiz Capitulino [this message]
2009-09-23 15:55   ` Markus Armbruster
2009-09-23 22:37 ` Markus Armbruster
2009-09-24 12:31   ` Luiz Capitulino
2009-09-24 12:44     ` Avi Kivity
2009-09-24 13:05       ` Luiz Capitulino
2009-09-24 13:07         ` Avi Kivity
2009-09-24 13:14           ` Luiz Capitulino
2009-11-11  9:59             ` [Qemu-devel] " Michael S. Tsirkin
2009-09-24 13:28     ` [Qemu-devel] " Markus Armbruster
2009-09-24 19:09       ` Luiz Capitulino
2009-11-11 10:03       ` [Qemu-devel] " Michael S. Tsirkin
2009-11-13  8:38         ` Markus Armbruster

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=20090923112129.4c3bff63@doriath \
    --to=lcapitulino@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=berrange@redhat.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).