From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu] qom: Document qom/device-list-properties implementation specific
Date: Wed, 2 May 2018 11:11:51 +0200 [thread overview]
Message-ID: <6c49e4ab-bb40-cf20-629a-2fc5c19d8585@redhat.com> (raw)
In-Reply-To: <87muxi8t2b.fsf@dusky.pond.sub.org>
On 02/05/2018 08:34, Markus Armbruster wrote:
> Alexey Kardashevskiy <aik@ozlabs.ru> writes:
>
>> On 30/4/18 7:39 pm, Paolo Bonzini wrote:
>>> On 30/04/2018 08:52, Alexey Kardashevskiy wrote:
>>>> diff --git a/qapi/misc.json b/qapi/misc.json
>>>> index 5636f4a..399ec74 100644
>>>> --- a/qapi/misc.json
>>>> +++ b/qapi/misc.json
>>>> @@ -1491,6 +1491,10 @@
>>>> #
>>>> # List properties associated with a device.
>>>> #
>>>> +# Note: the handler creates a device object, enumerates properties and destroys
>>>> +# the object so it only lists properties defined in DeviceClass::props or
>>>> +# created by DeviceClass::init()/TypeInfo::instance_init().
>>>> +#
>>>> # @typename: the type name of a device
>>>> #
>>>> # Returns: a list of ObjectPropertyInfo describing a devices properties
>>>> @@ -1506,6 +1510,11 @@
>>>> #
>>>> # List properties associated with a QOM object.
>>>> #
>>>> +# Note: the handler creates an object, enumerates properties and destroys
>>>> +# the object so it only lists properties created in TypeInfo::instance_init().
>>>> +# Since the instance_init() callback of the device object adds
>>>> +# DeviceClass::props as object properties, they will be listed as well.
>>>> +#
>>>
>>> This says what it does, but not why it is a problem. Can you explain
>>> that to me as well?
>>
>> It probably is not unless someone adds properties in realize() callback,
>
> Now work that into the doc comment, please :)
Are there any examples? If not, that belongs in a comment in the code
rather than the QAPI doc comment. If yes, then the doc comment should
include one.
Paolo
next prev parent reply other threads:[~2018-05-02 9:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 0:25 [Qemu-devel] [PATCH qemu v4 0/2] qmp: Add qom-list-properties to list QOM object properties Alexey Kardashevskiy
2018-03-03 0:25 ` [Qemu-devel] [PATCH qemu v4 1/2] qmp: Merge ObjectPropertyInfo and DevicePropertyInfo Alexey Kardashevskiy
2018-04-18 16:35 ` Eric Blake
2018-04-30 10:04 ` Paolo Bonzini
2018-03-03 0:25 ` [Qemu-devel] [PATCH qemu v4 2/2] qmp: Add qom-list-properties to list QOM object properties Alexey Kardashevskiy
2018-04-13 14:16 ` Markus Armbruster
2018-04-30 6:52 ` [Qemu-devel] [PATCH qemu] qom: Document qom/device-list-properties implementation specific Alexey Kardashevskiy
2018-04-30 6:56 ` no-reply
2018-04-30 7:07 ` Alexey Kardashevskiy
2018-04-30 6:58 ` no-reply
2018-04-30 7:00 ` no-reply
2018-04-30 9:39 ` Paolo Bonzini
2018-05-02 1:26 ` Alexey Kardashevskiy
2018-05-02 6:34 ` Markus Armbruster
2018-05-02 9:11 ` Paolo Bonzini [this message]
2018-05-02 9:33 ` Alexey Kardashevskiy
2018-05-02 9:50 ` Paolo Bonzini
2018-05-03 6:22 ` Alexey Kardashevskiy
2018-05-03 10:54 ` Paolo Bonzini
2018-05-02 9:38 ` Markus Armbruster
2018-05-02 9:47 ` Paolo Bonzini
2018-05-02 12:36 ` Markus Armbruster
2018-05-02 12:42 ` Paolo Bonzini
2018-05-02 13:31 ` Markus Armbruster
2018-05-02 13:32 ` Paolo Bonzini
2018-05-01 13:01 ` Eric Blake
2018-05-02 1:33 ` Alexey Kardashevskiy
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=6c49e4ab-bb40-cf20-629a-2fc5c19d8585@redhat.com \
--to=pbonzini@redhat.com \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--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).