From: Anthony Liguori <aliguori@us.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] vl: add -libvirt-caps option for libvirt to stop parsing help output
Date: Fri, 27 Jul 2012 10:27:27 -0500 [thread overview]
Message-ID: <87pq7hfcm8.fsf@codemonkey.ws> (raw)
In-Reply-To: <5012AE0D.6000806@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Il 26/07/2012 16:10, Anthony Liguori ha scritto:
>> Yup.
>>
>> You could do:
>>
>> qom-list-types implements=TYPE_DEVICE
>>
>> And that will give you the various types. We'll need to add a:
>>
>> device-list-properties typename=FOO
>>
>> I've got a patch locally for that that I'm testing right now. Paolo and
>> I never came to an agreement on how to do this generically for Objects
>> but I'm happy with a device-specific interface for the short term.
>
> I don't like the idea of using object_new, but it obviously works at
> least for now, so go ahead and call it qom-type-list-properties.
My patch doesn't use object_new() to do it. It uses static properties.
I'm going to try to push static properties to object. If I can do that
before 1.2, I'll rename this function to qom-type-list-properties.
Regards,
Anthony Liguori
>
> Paolo
next prev parent reply other threads:[~2012-07-27 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 19:47 [Qemu-devel] [PATCH] vl: add -libvirt-caps option for libvirt to stop parsing help output Anthony Liguori
2012-07-25 22:12 ` Eric Blake
2012-07-25 23:10 ` Anthony Liguori
2012-07-26 12:47 ` Daniel P. Berrange
2012-07-26 13:07 ` Daniel P. Berrange
2012-07-26 14:10 ` Anthony Liguori
2012-07-27 15:04 ` Paolo Bonzini
2012-07-27 15:27 ` Anthony Liguori [this message]
2012-07-27 11:23 ` Markus Armbruster
2012-07-27 11:49 ` Daniel P. Berrange
2012-07-27 12:19 ` Markus Armbruster
2012-07-27 16:35 ` Daniel P. Berrange
2012-07-27 17:17 ` Markus Armbruster
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=87pq7hfcm8.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).