On 12/05/2025 16.41, BALATON Zoltan wrote:
On Mon, 12 May 2025, Xiaoyao Li wrote:
...
We need something in code to restrict the *internal* property really
internal, i.e., not user settable. What the name of the property is
doesn't matter.
What's an internal property? Properties are there to make some field of an
object introspectable and settable from command line and QEMU monitor or
other external interfaces. If that's not needed for something why is it
defined as a property in the first place and not just e.g. C accessor
functions as part of the device's interface instead? I think this may be
overusing QOM for things that may not need it and adding complexity where
not needed.
Maybe some things could easily be simplified indeed, but for some others,
it's currently the way it's deeply rooted in the logic of QEMU. Have a look
at the hw_compat arrays in hw/core/machine.c ... it all goes via properties,
so there is certainly no easy and quick solution for this.
Thomas
