Alex Williamson <alex.william...@redhat.com> writes: > Create properties to be able to define speeds and widths for PCIe > links. The only tricky bit here is that our get and set callbacks > translate from the fixed QAPI automagic enums to those we define > in PCI code to represent the actual register segment value.
QAPI can only generate enumerations with values 0, 1, 2, ... You want different enumeration values, namely the actual register values. You still want QAPI to get its standard mapping to and from strings. This patch's solution is to define a non-QAPI enumeration type with the values you want [PATCH 1/9], then map between the enumerations in the PropertyInfo methods. Works. You could instead use the encoding chosen by QAPI for the properties, and map it to the register values on use. Differently ugly. Might be simpler. Your choice to make. We could extend QAPI to permit specification of the enumeration values. Marc-André's work to permit conditionals makes the syntax flexible enough to support that. Of course, adding QAPI features is worthwhile only if we get sufficient mileage out of them to result in an overall improvement. Even if we decided to do it right now, I'd recommend not to wait for it, but instead plan to simplify after the feature lands. > Cc: Eric Blake <ebl...@redhat.com> > Cc: Markus Armbruster <arm...@redhat.com> > Tested-by: Geoffrey McRae <ge...@hostfission.com> > Signed-off-by: Alex Williamson <alex.william...@redhat.com> Reviewed-by: Markus Armbruster <arm...@redhat.com>
