qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Eric Blake <eblake@redhat.com>,
	qemu-devel@nongnu.org, mprivozn@redhat.com, kraxel@redhat.com,
	amit.shah@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.1 v3 0/2] help libvirt know what's up with qga
Date: Thu, 26 Jun 2014 22:16:58 +0200	[thread overview]
Message-ID: <53AC7FBA.8050101@redhat.com> (raw)
In-Reply-To: <53AC4C4F.1050708@redhat.com>

On 06/26/14 18:37, Eric Blake wrote:
> On 06/26/2014 09:50 AM, Laszlo Ersek wrote:
>> Changes in v3: patch 1 creates the event with a "bool" field called
>> "open" in the data portion, instead of introducing a two-valued enum.
>> Patch 2 is left intact. Retested.
>>
>> Laszlo Ersek (2):
>>   virtio-serial: report frontend connection state via monitor
>>   char: report frontend open/closed state in 'query-chardev'
> 
> Series:
> Reviewed-by: Eric Blake <eblake@redhat.com>
> 
>>
>>  qapi-event.json          | 14 ++++++++++++++
>>  qapi-schema.json         |  8 +++++++-
>>  hw/char/virtio-console.c | 12 +++++++++---
>>  monitor.c                |  1 +
>>  qemu-char.c              |  1 +
>>  qmp-commands.hx          | 19 ++++++++++++++-----
>>  6 files changed, 46 insertions(+), 9 deletions(-)
> 
> Luiz is probably going to revive qmp-events.txt, at which point that
> file will need to be patched in a followup patch; I can help with that
> process (it's documentation-only, so safe to take even after hard freeze).

If it helps, here's two examples in advance (also, note to self):

2014-06-26 15:41:37.895+0000: 1637: debug :
qemuMonitorJSONIOProcessLine:172 : QEMU_MONITOR_RECV_EVENT:
mon=0x7f2e2400cfd0 event={"timestamp": {"seconds": 1403797297,
"microseconds": 895242}, "event": "VSERPORT_CHANGE", "data": {"open":
true, "id": "channel0"}}

2014-06-26 15:41:40.878+0000: 1637: debug :
qemuMonitorJSONIOProcessLine:172 : QEMU_MONITOR_RECV_EVENT:
mon=0x7f2e2400cfd0 event={"timestamp": {"seconds": 1403797300,
"microseconds": 878169}, "event": "VSERPORT_CHANGE", "data": {"open":
false, "id": "channel0"}}

Thanks
Laszlo

  reply	other threads:[~2014-06-26 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 15:50 [Qemu-devel] [PATCH for-2.1 v3 0/2] help libvirt know what's up with qga Laszlo Ersek
2014-06-26 15:50 ` [Qemu-devel] [PATCH for-2.1 v3 1/2] virtio-serial: report frontend connection state via monitor Laszlo Ersek
2014-06-27  4:45   ` Amit Shah
2014-06-27 12:32     ` Luiz Capitulino
2014-06-26 15:50 ` [Qemu-devel] [PATCH for-2.1 v3 2/2] char: report frontend open/closed state in 'query-chardev' Laszlo Ersek
2014-06-26 16:37 ` [Qemu-devel] [PATCH for-2.1 v3 0/2] help libvirt know what's up with qga Eric Blake
2014-06-26 20:16   ` Laszlo Ersek [this message]
2014-06-26 20:18     ` Laszlo Ersek
2014-06-27 13:36 ` 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=53AC7FBA.8050101@redhat.com \
    --to=lersek@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mprivozn@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).