commit | ce89a37c177728bdf9f032f1d4ef3ca07f9ac382 | [log] [tgz] |
---|---|---|
author | Manojkiran Eda <manojkiran.eda@gmail.com> | Wed Feb 05 23:09:04 2025 +0530 |
committer | Zhikui Ren <zhikui.ren@intel.com> | Tue Mar 18 19:36:10 2025 +0000 |
tree | 36497a4831a5f887fa66e94df0d379dcf3156493 | |
parent | f3b25e55311cf100b9b496a2ce24628bd8949bc7 [diff] |
smbios-mdr:Add support to toggle pcieslot presence In the current state, the PCIeslot presence is always hardcoded to `true`, since the PCIeSlots are always embedded on the board. But the slot presence is not really useful. Since we are already getting the current usage of the slot in the SMBIOS Type 9 structure we could use the "Available"/"Occupied" status in the current usage field to indicate the drive presence. Modify the slot presence code to only mark "true" if the current usage of the slot is "Occupied" & make it "false" if it is anything other than that. Tested By: 1. Enabled the meson option via the meta-ibm layer by adding PACKAGECONFIG:append = "slot-drive-presence" 2. Post the SMBIOS transfer, could see the presence of the slot being toggled with respect to the current occupancy of the slot. Change-Id: I57e6f48dc501e7e1625a5389ea1e989c5e585824 Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.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).