From: Stefan Hajnoczi <stefanha@gmail.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] QMP: add get_events(wait=True) option
Date: Thu, 26 May 2011 09:03:49 +0100 [thread overview]
Message-ID: <BANLkTimq1mAkuB4Rqp8ZvrFHN8wfzL97wA@mail.gmail.com> (raw)
In-Reply-To: <20110525181522.42eb9a70@doriath>
On Wed, May 25, 2011 at 10:15 PM, Luiz Capitulino
<lcapitulino@redhat.com> wrote:
> On Wed, 25 May 2011 19:48:00 +0100
> Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> wrote:
>
>> The get_events() function polls for new QMP events and then returns. It
>> can be useful to wait for the next QMP event so add the boolean 'wait'
>> keyword argument.
>>
>> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
>> ---
>> QMP/qmp.py | 11 ++++++++---
>> 1 files changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/QMP/qmp.py b/QMP/qmp.py
>> index 14ce8b0..2565508 100644
>> --- a/QMP/qmp.py
>> +++ b/QMP/qmp.py
>> @@ -43,7 +43,7 @@ class QEMUMonitorProtocol:
>> family = socket.AF_UNIX
>> return socket.socket(family, socket.SOCK_STREAM)
>>
>> - def __json_read(self):
>> + def __json_read(self, only_event=False):
>> while True:
>> data = self.__sockfile.readline()
>> if not data:
>> @@ -51,7 +51,8 @@ class QEMUMonitorProtocol:
>> resp = json.loads(data)
>> if 'event' in resp:
>> self.__events.append(resp)
>> - continue
>> + if not only_event:
>> + continue
>> return resp
>>
>> error = socket.error
>> @@ -106,9 +107,11 @@ class QEMUMonitorProtocol:
>> qmp_cmd['id'] = id
>> return self.cmd_obj(qmp_cmd)
>>
>> - def get_events(self):
>> + def get_events(self, wait=False):
>> """
>> Get a list of available QMP events.
>> +
>> + @param wait: block until an event is available (bool)
>> """
>> self.__sock.setblocking(0)
>> try:
>> @@ -118,6 +121,8 @@ class QEMUMonitorProtocol:
>> # No data available
>> pass
>> self.__sock.setblocking(1)
>> + if not self.__events and wait:
>> + self.__json_read(only_event=True)
>> return self.__events
>
> Maybe this is better (untested):
I've tested it because that's how I implemented it first too :).
However, I don't want to block until the QMP monitor sends the next
event when there is already a received event pending.
The patch I posted polls for new events first, then only blocks if
there are no events available.
Stefan
next prev parent reply other threads:[~2011-05-26 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 18:48 [Qemu-devel] [PATCH 1/2] QMP: add get_events(wait=True) option Stefan Hajnoczi
2011-05-25 18:48 ` [Qemu-devel] [PATCH 2/2] QMP: add server mode to QEMUMonitorProtocol Stefan Hajnoczi
2011-05-25 21:16 ` Luiz Capitulino
2011-05-26 8:16 ` Stefan Hajnoczi
2011-05-25 21:15 ` [Qemu-devel] [PATCH 1/2] QMP: add get_events(wait=True) option Luiz Capitulino
2011-05-26 8:03 ` Stefan Hajnoczi [this message]
2011-05-26 12:47 ` Luiz Capitulino
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=BANLkTimq1mAkuB4Rqp8ZvrFHN8wfzL97wA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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).