Huang, Kai wrote: [..] > > Given this is JSON any plan to just check-in "global_metadata.json" > > somewhere in tools/ with a script that queries for a set of fields and > > spits them out into a Linux data structure + set of TD_SYSINFO_*_MAP() > > calls? Then no future review bandwidth needs to be spent on manually > > checking offsets names and values, they will just be pulled from the > > script. > > This seems a good idea. I'll add this to my TODO list and evaluate it > first. > > One minor issue is some metadata fields may need special handling. E.g., > MAX_VCPUS_PER_TD (which is u16) may not be supported by some old TDX > modules, but this isn't an error because we can just treats it as > U16_MAX. TDX Module had better not be breaking us when they remove metadata fields. So if you know of fields that get removed the module absolutely cannot cause existing code paths. Linux could maybe grant that some values start returning an explicit "deprecated" error code in the future and Linux adds handling for that common case. Outside of that metadata fields are forever and the module needs to ship placeholder values that fail gracefully on older kernels. OS software should not be expected to keep up with the whims of metadata field removals without an explicit plan to make those future removals benign to legacy kernels.
