From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Steve Sistare <steven.sistare@oracle.com>, qemu-devel@nongnu.org
Cc: John Snow <jsnow@redhat.com>, Cleber Rosa <crosa@redhat.com>,
Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@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>
Subject: Re: [PATCH V3 1/3] qom: qom-list-getv
Date: Thu, 10 Jul 2025 09:13:24 +0200 [thread overview]
Message-ID: <557f877a-f2e4-4c89-8b77-ae89a19486df@linaro.org> (raw)
In-Reply-To: <44e6c0e9-927f-492d-9a2a-c26f2509e409@linaro.org>
On 8/7/25 23:54, Philippe Mathieu-Daudé wrote:
> On 8/7/25 19:24, Steve Sistare wrote:
>> Define the qom-list-getv command, which fetches all the properties and
>> values for a list of paths. This is faster than qom-tree-get when
>> fetching a subset of the QOM tree. See qom.json for details.
>>
>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
>> ---
>> qapi/qom.json | 50 ++++++++++++++++++++++++++++++++++++++++++++
>> ++++++
>> qom/qom-qmp-cmds.c | 53 ++++++++++++++++++++++++++++++++++++++++++++
>> +++++++++
>> 2 files changed, 103 insertions(+)
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
and:
Tested-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2025-07-10 7:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 17:24 [PATCH V3 0/3] fast qom tree get Steve Sistare
2025-07-08 17:24 ` [PATCH V3 1/3] qom: qom-list-getv Steve Sistare
2025-07-08 21:54 ` Philippe Mathieu-Daudé
2025-07-10 7:13 ` Philippe Mathieu-Daudé [this message]
2025-07-09 8:39 ` Markus Armbruster
2025-07-09 15:19 ` Steven Sistare
2025-07-08 17:24 ` [PATCH V3 2/3] python: use qom-list-getv Steve Sistare
2025-07-08 17:24 ` [PATCH V3 3/3] tests/qtest/qom-test: unit test for qom-list-getv Steve Sistare
2025-07-08 17:47 ` Fabiano Rosas
2025-07-08 22:02 ` Philippe Mathieu-Daudé
2025-07-09 6:23 ` Markus Armbruster
2025-07-09 15:17 ` Steven Sistare
2025-07-10 7:12 ` Philippe Mathieu-Daudé
2025-07-10 8:54 ` Markus Armbruster
2025-07-10 15:58 ` 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=557f877a-f2e4-4c89-8b77-ae89a19486df@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--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=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 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).