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 v2 2/2] char: report frontend open/close


From: Eric Blake
Subject: Re: [Qemu-devel] [PATCH for-2.1 v2 2/2] char: report frontend open/closed state in 'query-chardev'
Date: Thu, 26 Jun 2014 06:09:11 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0

On 06/26/2014 05:11 AM, Laszlo Ersek wrote:
> In addition to the on-line reporting added in the previous patch, allow
> libvirt to query frontend state independently of events.
> 
> Libvirt's path to identify the guest agent channel it cares about differs
> between the event added in the previous patch and the QMP response field
> added here. The event identifies the frontend device, by "id". The
> 'query-chardev' QMP command identifies the backend device (again by "id").
> The association is under libvirt's control.
> 
> RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1080376
> Signed-off-by: Laszlo Ersek <address@hidden>
> ---
> 

>  ##
> -{ 'type': 'ChardevInfo', 'data': {'label': 'str', 'filename': 'str'} }
> +{ 'type': 'ChardevInfo', 'data': {'label': 'str',
> +                                  'filename': 'str',
> +                                  'frontend-open': 'bool'} }

Hmm; I wonder if this should instead be
'frontend-status':'VirtioSerialPortStatus', to reuse the type from patch
1/2.  That way, if we ever add a third state, then both the event and
the poll will be reusing the same enum values to report that state.


-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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