From: Markus Armbruster <armbru@redhat.com>
To: Steven Sistare <steven.sistare@oracle.com>
Cc: qemu-devel@nongnu.org, John Snow <jsnow@redhat.com>,
Cleber Rosa <crosa@redhat.com>, Eric Blake <eblake@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>,
Fabiano Rosas <farosas@suse.de>,
Laurent Vivier <lvivier@redhat.com>,
Peter Krempa <pkrempa@redhat.com>,
devel@lists.libvirt.org
Subject: Re: [PATCH V2 1/5] qom: qom-tree-get
Date: Tue, 08 Jul 2025 08:53:55 +0200 [thread overview]
Message-ID: <87cyabyxz0.fsf@pond.sub.org> (raw)
In-Reply-To: <87zfdfz2y6.fsf@pond.sub.org> (Markus Armbruster's message of "Tue, 08 Jul 2025 07:06:25 +0200")
Markus Armbruster <armbru@redhat.com> writes:
> Steven Sistare <steven.sistare@oracle.com> writes:
>
>> On 7/4/2025 8:22 AM, Markus Armbruster wrote:
>>> Steve Sistare <steven.sistare@oracle.com> writes:
>>>
>>>> Define the qom-tree-get QAPI command, which fetches an entire tree of
>>>> properties and values with a single QAPI call. This is much faster
>>>> than using qom-list plus qom-get for every node and property of the
>>>> tree. See qom.json for details.
>>>>
>>>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
>>>> ---
>>>> qapi/qom.json | 56 ++++++++++++++++++++++++++++++++++++++++++
>>>> qom/qom-qmp-cmds.c | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 2 files changed, 128 insertions(+)
>>>>
>>>> diff --git a/qapi/qom.json b/qapi/qom.json
>>>> index 28ce24c..94662ad 100644
>>>> --- a/qapi/qom.json
>>>> +++ b/qapi/qom.json
[...]
>>>> ##
>>>> +# @qom-tree-get:
>>>> +#
>>>> +# This command returns a tree of objects and their properties,
>>>> +# rooted at the specified path.
>>>> +#
>>>> +# @path: The absolute or partial path within the object model, as
>>>> +# described in @qom-get
>>>> +#
>>>> +# Errors:
>>>> +# - If path is not valid or is ambiguous, returns an error.
>>>
>>> By convention, we use "If <condition>, <error>, where <error> is a
>>> member of QapiErrorClass.
>>
>> OK. I was following the minimal Errors examples from this same file.
>
> Yup. I'll clean them up.
I changed my mind.
Omitting ", <error>" is fairly common, actually. I don't feel like
chasing down the actual error classes. Moreover, documenting error
classes we don't want people to use seems counterproductive.
Feel free to just delete ", returns an error." and call it a day.
[...]
next prev parent reply other threads:[~2025-07-08 20:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 13:47 [PATCH V2 0/5] fast qom tree get Steve Sistare
2025-05-12 13:47 ` [PATCH V2 1/5] qom: qom-tree-get Steve Sistare
2025-07-04 12:22 ` Markus Armbruster
2025-07-07 14:44 ` Steven Sistare
2025-07-08 5:06 ` Markus Armbruster
2025-07-08 6:53 ` Markus Armbruster [this message]
2025-07-08 7:14 ` Philippe Mathieu-Daudé
2025-07-08 11:50 ` Steven Sistare
2025-07-08 15:17 ` Philippe Mathieu-Daudé
2025-05-12 13:47 ` [PATCH V2 2/5] python: use qom-tree-get Steve Sistare
2025-05-12 13:47 ` [PATCH V2 3/5] tests/qtest/qom-test: unit test for qom-tree-get Steve Sistare
2025-07-08 7:15 ` Philippe Mathieu-Daudé
2025-05-12 13:47 ` [PATCH V2 4/5] qom: qom-list-getv Steve Sistare
2025-07-04 12:22 ` Markus Armbruster
2025-07-07 14:40 ` Steven Sistare
2025-07-08 4:41 ` Markus Armbruster
2025-05-12 13:47 ` [PATCH V2 5/5] tests/qtest/qom-test: unit test for qom-list-getv Steve Sistare
2025-05-19 21:19 ` [PATCH V2 0/5] fast qom tree get Fabiano Rosas
2025-07-04 12:26 ` Markus Armbruster
2025-07-07 14:39 ` Steven Sistare
2025-07-04 12:33 ` Markus Armbruster
2025-07-07 14:39 ` Steven Sistare
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=87cyabyxz0.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=farosas@suse.de \
--cc=jsnow@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=steven.sistare@oracle.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.