On Wed, 2017-03-15 at 08:24 +0100, Gerd Hoffmann wrote: > > > > The short answer: emulating real hardware. > > Ok, that is reason enough. > > Adding bootonceindex everywhere doesn't look like the best plan to me > though. Possibly we can pimp up bootindex in a backward-compatible > way? > Something like bootindex=<normal>[.<once>] ?
That would (likely) avoid modifying all devices, but wouldn't that make the 'bootindex' property a string (now: 'int32') and thus change the QOM API? I did consider making device_add_bootindex_property() to automatically add the new property too, but since that API is currently such that the _caller_ provides the name of the added property, it would mean that the function would need to generate the second name using some magic mangling rule and that didn't seem very nice to me. Of course the API could be modified so that the caller provides two names, but then we are already back to modifying all relevant devices.
