We would like to adjust the CPU information sent by eos-metrics-instrumentation to include CPU flags: statistics about how widely-supported certain extensions are will allow the freedesktop-sdk project to quantify the impact of (for example) assuming certain x86-64 extensions are present.
Previously, events with some given UUID are expected to have a payload of one specific GVariant type, and those types are typically not something extensible like a{sv}. This is quite annoying when we want to add a new field, particularly in this CPU data which just ends up being stuffed into a JSONB column in the database.
So, allow event models to specify a tuple of accepted GVariant types; then take advantage of this in the ComputerInformation model to understand a new type with an extra string of CPU flags.
We would like to adjust the CPU information sent by eos-metrics-instrumentation to include CPU flags: statistics about how widely-supported certain extensions are will allow the freedesktop-sdk project to quantify the impact of (for example) assuming certain x86-64 extensions are present.
Previously, events with some given UUID are expected to have a payload of one specific GVariant type, and those types are typically not something extensible like
a{sv}. This is quite annoying when we want to add a new field, particularly in this CPU data which just ends up being stuffed into a JSONB column in the database.So, allow event models to specify a tuple of accepted GVariant types; then take advantage of this in the ComputerInformation model to understand a new type with an extra string of CPU flags.
https://phabricator.endlessm.com/T35351