| commit | 6f9e7a7669efb430d43252a2bc8b9f7af5250332 | [log] [tgz] |
|---|---|---|
| author | Prithvi Pai <ppai@nvidia.com> | Fri Mar 14 13:05:02 2025 +0530 |
| committer | Prithvi Pai <ppai@nvidia.com> | Tue Apr 01 14:41:07 2025 +0530 |
| tree | 21ba7c082d2f244263afcdb5ea43104a53119e02 | |
| parent | 5af42bbf374907888c09d7aaf2cbf74d74c7707d [diff] |
smbios-mdr: Expose Firmware Inventory Information
SMBIOS Type 45 defines the data structure to expose Firmware
Inventory information. Added patch which exposes the same
on the DBus.
Introduced fw-inventory-dbus meson option which by default,
will be disabled. When enabled fw-inventory is exposed to dbus
Introduced expose-firmware-component-name meson option which
by default, will be disabled. When enabled fw-component name is
exposed as dbus object
Tested:
1) No crash is seen when firmware is flashed with change
2) Firmware Inventory information is available under dbus tree
```
busctl tree xyz.openbmc_project.Smbios.MDR_V2
`- /xyz
`- /xyz/openbmc_project
|- /xyz/openbmc_project/Smbios
| `- /xyz/openbmc_project/Smbios/MDR_V2
`- /xyz/openbmc_project/software
`- /xyz/openbmc_project/software/UEFI
```
Change-Id: If5b367f21dedc0addef4f7b1d4c6dac6a5dc17c2
Signed-off-by: Prithvi Pai <ppai@nvidia.com>
The main application in this repo is smbiosmdrv2app, capable of parsing a binary SMBIOS table and publishing the system information on D-Bus, to be consumed by other OpenBMC applications.
The SMBIOS table is usually sent to the BMC by the host firmware (BIOS). The system designer can theoretically choose any transport and mechanism for sending the SMBIOS data, but there are at least two implementation today:
The primary API is a set of Intel OEM IPMI commands called Managed Data Region version 2 (MDRv2), which provides a means for host firmware to send data through the VGA shared memory region. MDRv2 has a concept of multiple agents, each maintaining a "directory" containing directory entries (aka data sets). The host can query for the existence and version of directories to determine when it needs to send an updated SMBIOS table.
intel-ipmi-oem implements the IPMI command handlers, routing commands and data to the correct agent (e.g. smbios-mdr). The D-Bus interface between the IPMI handler and smbios-mdr is largely a mirror of IPMI commands.
phosphor-ipmi-blobs is an alternative implementation of a generic IPMI blob transfer API. Compared to MDRv2, it is simpler and easier to use, but also transfers the data in-band with the IPMI commands and therefore slower than using a shared memory region (which may or may not be a concern).
phosphor-ipmi-blobs provides a blob manager shared library for ipmid which implements the IPMI commands. In turn, it loads blob handler libraries that each implement support for specific blobs. Here in smbios-mdr we provide such a blob handler for the /smbios blob. It works by writing the data into /var/lib/smbios/smbios2 (the local persistent cache for the SMBIOS table) and calling the AgentSynchronizeData D-Bus method to trigger smbios-mdr to reload and parse the table from that file.
cpuinfoapp is an Intel-specific application that uses I2C and PECI to gather more details about Xeon CPUs that aren't included in the SMBIOS table for some reason. It also implements discovery and control for Intel Speed Select Technology (SST).