On 11/16/2026 12:41 PM, Pierrick Bouvier wrote: > On 11/12/2026 5:30 AM, Daniel P. Berrangé wrote: >> All QOM types must have a globally unique typename, however, for >> user convenience, some might also want to have aliases which are >> permitted to be ambiguous. Define an "Aliased" interface which >> can be implemented by types which want to support aliases. >> >> When resolving an alias, if there are multiple QOM types with a >> matching alias this is considered an error. Ambiguity can be >> resolved by matching system state, with the selected target >> being the currently implemented filter. >> >> Signed-off-by: Daniel P. Berrangé <[email protected]> >> --- >> include/qom/object_interfaces.h | 77 +++++++++++++++++++++++++++++++++ >> qom/object_interfaces.c | 57 ++++++++++++++++++++++++ >> 2 files changed, 134 insertions(+) >> > > Looks good to me. > > Two open questions: > - Is that worth supporting more than one alias? When would we need that?
Seems like at least arm/virt need it due to explicit versioning. > - Yonggang mentioned the possibility to couple this with target, I'm not > sure we should go in this direction. What do you think about it? > > Regards, > Pierrick
