Hi,

Today smbios table is generated at boot time, as a static blob in reserved 
memory region.
Some of the info becomes stale following hot add/remove events which becomes
common nowadays.

I wonder if there is any alternative, or some discussions/plan in progress to 
solve this
problem? Any feedbacks/pointers are appreciated.


One idea is to make sysfs (/sys/firmware/dmi/) to be the source

of truth for all kernel and user space code which need to

consume smbios data. It looks like dmidecode hard codes

the memory region base 0xF0000, why don’t it pick up from /sys/firmware/dmi?



Thank you,

Jonathan

_______________________________________________
https://lists.nongnu.org/mailman/listinfo/dmidecode-devel

Reply via email to