commit | 06eb63003821ed050f8c578b5750ba48fca005f0 | [log] [tgz] |
---|---|---|
author | Josh Lehan <krellan@google.com> | Thu Feb 15 14:38:28 2024 -0800 |
committer | Josh Lehan <krellan@google.com> | Wed Feb 21 21:03:24 2024 +0000 |
tree | 609dc0a12da1478528c70965ba5fa6684fc3599e | |
parent | 0f7704a31e9f0f7c78466c1625eaa1b13b334c47 [diff] |
Enable support for SMBIOS version 3.4 As the currently supported 3.5 standard is a superset of 3.4, according to a glance at the https://www.dmtf.org/standards/smbios spec, enabling support for 3.4 should be as straightforward as simply adding it to this allowlist of supported versions. This change is inspired by the proposed https://github.com/openbmc/smbios-mdr/issues/6 which suggests a similar change for 3.1 version. The only reason I am not adding 3.1 at the same time here, is that I only have a 3.4 SMBIOS in the machine I am testing now. Tested: The SMBIOS from my host is no longer needlessly rejected for being of 3.4 version. Change-Id: I29bcb872377c87088b2ed4fc0ec90a03d89c15d8 Signed-off-by: Josh Lehan <krellan@google.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).