BALATON Zoltan <bala...@eik.bme.hu> writes:
> On Tue, 13 May 2025, Markus Armbruster wrote:
>> Mark Cave-Ayland <mark.caveayl...@nutanix.com> writes:
>>> On a related note this also brings us back to the discussion as to the
>>> relationship between qdev and QOM: at one point I was under the impression
>>> that qdev properties were simply QOM properties that were exposed
>>> externally, i.e on the commmand line for use with -device.
>>>
>>> Can you provide an update on what the current thinking is in this area, in
>>> particular re: scoping of qdev vs QOM properties?
>>
>> qdev is a leaky layer above QOM.
>>
>> qdev properties are also QOM properties.
>>
>> All device properties are exposed externally.
>
> That was clear but the question was if QOM properties (that are not qdev
> properties) exist and if so are they also exposed? If not exposed it may be
> used for internal properties (where simpler solutions aren't convenient) but
> maybe qdev also adds easier definition of properties that's why they used
> instead of QOM properties?
I'm afraid we haven't answered your question clearly, yet. The answer
is yes, QOM properties that are not qdev properties do exist. The first
one that comes along: ich9_pm_add_properties() adds a bunch to device
ICH9-LPC. They are exposted externally. To see them, try
$ qemu-system-x86_64 -device ICH9-LPC,help
[...]
