[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command
From: |
Eric Blake |
Subject: |
Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command |
Date: |
Mon, 13 May 2013 08:14:12 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5 |
On 05/13/2013 07:18 AM, Luiz Capitulino wrote:
>>>> Luiz, any idea how to do something like this, a QAPI enum with values
>>>> that are determined at runtime? Especially with respect to the coming
>>>> schema introspection?
>>>
>>> Or maybe we make the 'enum' list ALL possible types, but then add a
>>> query-* command that returns an array of only those enum values that are
>>> supported. Introspection would see all types, but the query command
>>> would be the useful variant that is runtime-dependent.
>
> Agreed. This is a capability, and we're adding query- commands to query
> capabilities.
>
>> Then is there any advantage in making it an enum in the first place?
>
> Eric is in a better position to answer this, but the fact that this can
> be queried isn't a strong pro for having it?
Hmm, you raise an interesting point - if we have a query-block-formats
command that returns an array of strings, then keep 'str' everywhere
else a format is required, that is no different for what is sent over
the wire compared to a query-block-formats that returns an array of
'BlockFormat' enum values, with the enum showing all possible formats
(even if support wasn't compiled in), and with 'BlockFormat' everywhere
else. Introspection-wise, you'd have to know that you call
query-block-formats instead of introspecting on the type of the format
argument, but information-wise, there's no loss of details if the query-
command provides the runtime list, and the remaining commands stick with
'str'. I still think an enum is a bit nicer from the type-safety
aspect, but I'm finding it hard to envision any scenario where libvirt
would have to resort to introspection if we have a query-block-formats
in place, and thus am not opposed to your idea of avoiding the enum.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, (continued)
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, Eric Blake, 2013/05/11
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, Kevin Wolf, 2013/05/13
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, Eric Blake, 2013/05/13
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, Kevin Wolf, 2013/05/13
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, Luiz Capitulino, 2013/05/13
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command,
Eric Blake <=
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, Kevin Wolf, 2013/05/13
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, Eric Blake, 2013/05/13
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, Wenchao Xia, 2013/05/13
- Re: [Qemu-devel] [PATCH v2 2/3] block: add block-backup QMP command, Stefan Hajnoczi, 2013/05/14
[Qemu-devel] [PATCH v2 1/3] block: add basic backup support to block driver, Stefan Hajnoczi, 2013/05/01