On Fri, Jun 14, 2013 at 12:09:33PM +0100, Eric Blake wrote:
> On 06/14/2013 10:52 AM, Amos Kong wrote:
> > +const char *type;
> > +const char *name;
> > +const char *data;
> > +const char *returns;
> > +} qmp_schema_table[] = {
> > +"""
> > +
> > +for i in exprs_all[1]:
> > +print i
> > +
> >
On 06/14/2013 10:52 AM, Amos Kong wrote:
>>From 2b39fe0f380eea6a96de3589b3d148673d28c1ff Mon Sep 17 00:00:00 2001
> From: Amos Kong
> Date: Fri, 7 Jun 2013 18:02:21 +0800
> Subject: [PATCH] full introspection support for QMP
>
> Signed-off-by: Amos Kong
> ---
> qapi-schema.json | 6 ++
On 06/14/2013 10:52 AM, Amos Kong wrote:
> On Fri, Jun 07, 2013 at 06:17:26PM +0800, Amos Kong wrote:
>> On Fri, Jun 07, 2013 at 06:12:30PM +0800, Amos Kong wrote:
>>> Sent out a draft patch in the end of this week. It doesn't support:
>>> * output all stuffs in one shot.
>>> * introspect event
>>>
On Fri, Jun 07, 2013 at 06:12:30PM +0800, Amos Kong wrote:
> Sent out a draft patch in the end of this week. It doesn't support:
> * output all stuffs in one shot.
> * introspect event
> * provide metadata date
>
> How can we define a dynamic dict in qmp-schema.json ?
>
> Currently I just output
Sent out a draft patch in the end of this week. It doesn't support:
* output all stuffs in one shot.
* introspect event
* provide metadata date
How can we define a dynamic dict in qmp-schema.json ?
Currently I just output the raw json dict by a string, Libvirt needs
parse two times, convert the s
Am 23.05.2013 um 15:52 hat Anthony Liguori geschrieben:
> Kevin Wolf writes:
>
> > Am 23.05.2013 um 14:08 hat Anthony Liguori geschrieben:
> >> Kevin Wolf writes:
> >>
> >>
> >> There are two things here: the schema and the generated code. The
> >> generated code can and should live in the mo
On 05/23/2013 07:52 AM, Anthony Liguori wrote:
>> libvirt already knows how to use features. It must know it, just parsing
>> the schema doesn't automagically give you libvirt code, so someone must
>> have coded the libvirt side of things. The interesting part is whether a
>> given interface is ava
Kevin Wolf writes:
> Am 23.05.2013 um 14:08 hat Anthony Liguori geschrieben:
>> Kevin Wolf writes:
>>
>>
>> There are two things here: the schema and the generated code. The
>> generated code can and should live in the module.
>>
>> But the schema always stays the same.
>>
>> Think of the s
On 05/22/2013 07:40 AM, Amos Kong wrote:
> Hi all,
>
> We already have query-command-line-options to query details of command-line
> options. As we discussed in the list, we also need full introspection of QMP
> (command). The qmp-events also need to be dumped, we can define events in
> qai-schema
Am 23.05.2013 um 14:08 hat Anthony Liguori geschrieben:
> Kevin Wolf writes:
>
> > Am 22.05.2013 um 18:14 hat Anthony Liguori geschrieben:
> >> Kevin Wolf writes:
> >> > For example, libvirt wants to query which block drivers it can use. It
> >> > doesn't really matter for which drivers we had t
Luiz Capitulino writes:
> On Thu, 23 May 2013 07:08:59 -0500
> Anthony Liguori wrote:
>
>> > then we don't need introspection at all. There's no user for it then.
>>
>> Introspection is not the right approach to feature discovery. The
>> schema does answer the question of what features are ena
On Thu, 23 May 2013 07:08:59 -0500
Anthony Liguori wrote:
> > then we don't need introspection at all. There's no user for it then.
>
> Introspection is not the right approach to feature discovery. The
> schema does answer the question of what features are enabled, it just
> answers the questio
Kevin Wolf writes:
> Am 22.05.2013 um 18:14 hat Anthony Liguori geschrieben:
>> Kevin Wolf writes:
>> > For example, libvirt wants to query which block drivers it can use. It
>> > doesn't really matter for which drivers we had the source initially, but
>> > only which drivers are compiled in (po
Am 22.05.2013 um 18:14 hat Anthony Liguori geschrieben:
> Kevin Wolf writes:
>
> > Am 22.05.2013 um 15:40 hat Amos Kong geschrieben:
> >> Hi all,
> >>
> >> We already have query-command-line-options to query details of command-line
> >> options. As we discussed in the list, we also need full int
On Wed, 22 May 2013 21:40:07 +0800
Amos Kong wrote:
> Hi all,
>
> We already have query-command-line-options to query details of command-line
> options. As we discussed in the list, we also need full introspection of QMP
> (command). The qmp-events also need to be dumped, we can define events in
Kevin Wolf writes:
> Am 22.05.2013 um 15:40 hat Amos Kong geschrieben:
>> Hi all,
>>
>> We already have query-command-line-options to query details of command-line
>> options. As we discussed in the list, we also need full introspection of QMP
>> (command). The qmp-events also need to be dumped,
Am 22.05.2013 um 15:40 hat Amos Kong geschrieben:
> Hi all,
>
> We already have query-command-line-options to query details of command-line
> options. As we discussed in the list, we also need full introspection of QMP
> (command). The qmp-events also need to be dumped, we can define events in
> q
Hi all,
We already have query-command-line-options to query details of command-line
options. As we discussed in the list, we also need full introspection of QMP
(command). The qmp-events also need to be dumped, we can define events in
qai-schema.json. We can also dump QMP errors in future if it's
18 matches
Mail list logo
