qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH for-2.1 v3 0/2] help libvirt know what's up with


From: Laszlo Ersek
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
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

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 <address@hidden>
> 
>>
>>  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 via email to

[Prev in Thread] Current Thread [Next in Thread]