Any device in the QOM tree could have an alias. Why would you want
to limit the possible aliases? a part from dynamic ones.

I was thinking in terms of automatically populating some entries e.g. for PCI 
buses, but from below I see this is not considered a good idea :)

Ah. I imagine that once the container is available, the machine, the SoC,
buses, devices could populate it however they see fit.

When you say any *device* above, are you thinking of a specific restriction to 
devices, since I can see this would be useful for some buses too?

The const link should apply to any QOM object I think. Give it a try :)

which ones are added automatically,

That's dangerous. I would say none.

Fair enough. Should we enforce some basic rules e.g. all lower-case, no spaces, 
mandatory index suffix to try and keep things a bit consistent? (basically as 
they would appear in Open Firmware).

I don't think QEMU necessarily needs to follow the naming convention
of Open Firmware specification. A PPC or ARM machine could make sure
the names are compatible though or would you like the machine_add_alias()
helper to implement some dt fixup ?

Perhaps these should be enforced programmatically?

Well, if it is a key requirement for a machine, perhaps it can be
implemented at the machine level. What do you have in mind ?

Cheers,

C.


Reply via email to