From: Anthony Liguori <aliguori@us.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Ronen Hod <rhod@redhat.com>,
Amos Kong <akong@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: Full introspection support for QMP
Date: Thu, 23 May 2013 07:52:15 -0500 [thread overview]
Message-ID: <871u8xq2o0.fsf@codemonkey.ws> (raw)
In-Reply-To: <20130523084009.743e187f@redhat.com>
Luiz Capitulino <lcapitulino@redhat.com> writes:
> On Thu, 23 May 2013 07:08:59 -0500
> Anthony Liguori <aliguori@us.ibm.com> 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 question of what the signature of the methods are.
>
> (s/does answer/does not answer)
Yes, -ENOCAFFIENE :-/
> But there's an intersection here: a new enum value or new argument can
> be a new feature too.
>
> If we add new commands to query features, than I'm afraid that in the
> long run feature discovery will be split in query-qmp-schema and the
> specific feature discovery commands.
>
> I'm not arguing in favor of one or another way, but we need to know
> why and where we're going. The real motivation behind full introspection
> is to allow commands to be extended.
Right, so let's look at some examples and see how the introspection
would work for feature detection vs. some other form of feature
detection.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2013-05-23 12:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 13:40 [Qemu-devel] RFC: Full introspection support for QMP Amos Kong
2013-05-22 14:44 ` Kevin Wolf
2013-05-22 16:14 ` Anthony Liguori
2013-05-23 8:18 ` Kevin Wolf
2013-05-23 12:08 ` Anthony Liguori
2013-05-23 12:40 ` Luiz Capitulino
2013-05-23 12:52 ` Anthony Liguori [this message]
2013-05-23 12:54 ` Kevin Wolf
2013-05-23 13:52 ` Anthony Liguori
2013-05-23 14:17 ` Eric Blake
2013-05-23 14:29 ` Kevin Wolf
2013-05-22 17:56 ` Luiz Capitulino
2013-05-23 12:58 ` Eric Blake
2013-06-07 10:12 ` [Qemu-devel] RFC: Full introspection support for QMP (with draft patch) Amos Kong
2013-06-07 10:17 ` Amos Kong
2013-06-14 9:52 ` Amos Kong
2013-06-14 10:59 ` Eric Blake
2013-06-14 11:09 ` Eric Blake
2013-06-18 12:21 ` Amos Kong
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=871u8xq2o0.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=akong@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rhod@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.