qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2] Show values and description when using "qom-


From: Markus Armbruster
Subject: Re: [Qemu-devel] [PATCH v2] Show values and description when using "qom-list"
Date: Tue, 12 Jun 2018 08:02:26 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Andreas Färber <address@hidden> writes:

> Am 08.06.2018 um 11:41 schrieb Dr. David Alan Gilbert:
>> * Andreas Färber (address@hidden) wrote:
>>> Am 01.06.2018 um 17:39 schrieb Ricardo Perez Blanco:
>>>> For debugging purposes it is very useful to:
>>>>  - See the description of the field. This information is already filled
>>>>    in but not shown in "qom-list" command.
>>>
>>> No objection on this part.
>>>
>>>>  - Display value of the field.
>>>
>>> That is by definition the qom-get operation, not qom-list. Just like the
>>> ls command does not show file contents, there's cat etc. for that. For
>>> debugging purposes we had a qom-tree (?) command that would combine
>>> both.
>>
>> I'm not too bothered about distinguishing between the two commands;
>> but it would be nice

When an HMP and QMP both have a command with the same name, they should
do the same.

HMP may add convenience features that aren't wanted in QMP, but I feel
extending an operation to list objects to also show their contents goes
beyond that.  If we want an HMP command that does both, it should be
named differently.  Perhaps that might even be more appropriate for HMP
than low-level commands qom-list and qom-get, but I leave that to the
HMP maintainer to decide.

>>                      - one reason I'm not too bothered is because we've
>> failed to get a qom-get in multiple years of trying.

We clearly haven't tried hard enough.

If we can figure out how to show values in qom-list, surely we can
figure out how to show them in qom-get.

>>>       There might be unmerged patches on qemu-devel related to display
>>> of certain data types.
>> 
>> Which ones?
>
> My original qom-info series needed StringOutputVisitor changes for enums
> (test case: rtc) that did not get accepted immediately and thus some
> part of HMP qom-info/qom-get got stuck due to risking assertions for
> qom-info / otherwise; QMP was not affected IIRC.

Here's the last try I can find:
[PATCH v2] qom: Implement qom-get HMP command
Message-Id: <address@hidden>
https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg01041.html

Its v1 tries a different approach:
[PATCH 0/2] qom-get [for 2.8]
Message-Id: <address@hidden>
Unfortunately the mailing list archive doesn't show the full thread, so
you get to follow three links:
https://lists.gnu.org/archive/html/qemu-devel/2016-08/msg03815.html
https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg04261.html
https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg04267.html



reply via email to

[Prev in Thread] Current Thread [Next in Thread]