Google Git
Sign in
gbmc / pldm / refs/heads/master
commit28ba36aa9ecc3b4e8f2c2f8b2821dd8ec8c83d78[log] [tgz]
authorPavithra Barithaya <pavithrabarithaya07@gmail.com>Thu Apr 24 16:36:18 2025 +0530
committerPavithra Barithaya <pavithrabarithaya07@gmail.com>Thu Dec 11 09:32:08 2025 +0000
treec61d5b08a0edcee814992d3891512ffc913c6fbc
parentd237a65d3b12920963951310a015dddbcce03b40 [diff]
fru: Function to remove the individual FRU Record

When there is a concurrent maintenance operation a FRU can be
removed or added. When the FRU is removed we must make sure that
the associated FRU Record set PDRs, State Effecter PDRs, State
Sensor PDRs, EntityAssociation PDRs need to be removed from the
repository. This commit adds the function that does the required
functionality.

Tested: Removal of a FRU say a Fan by making the present property
of the FRU as false. This action removes the corresponding
FRURecordSet PDRs, State effecter PDRs, State sensor PDRs and
also the Entity association PDRs from the repo. This also removes
the node corresponding to that FRU from the entity association
tree.
This behavior is observed for other FRUs as well.

Change-Id: I6c6e17e21807940ce6d4a230dbceafd9f7c5c958
Signed-off-by: Pavithra Barithaya <pavithrabarithaya07@gmail.com>
4 files changed
tree: c61d5b08a0edcee814992d3891512ffc913c6fbc
  1. common/
  2. configurations/
  3. docs/
  4. fw-update/
  5. host-bmc/
  6. libpldmresponder/
  7. oem/
  8. platform-mc/
  9. pldmd/
  10. pldmtool/
  11. requester/
  12. softoff/
  13. subprojects/
  14. test/
  15. tools/
  16. utilities/
  17. .clang-format
  18. .clang-tidy
  19. .eslintignore
  20. .gitignore
  21. .linter-ignore
  22. LICENSE
  23. meson.build
  24. meson.options
  25. OWNERS
  26. README.md
README.md

PLDM - Platform Level Data Model

License

Overview

PLDM (Platform Level Data Model) is a key component of the OpenBMC project, providing a standardized data model and message formats for various platform management functionalities. It defines a method to manage, monitor, and control the firmware and hardware of a system.

The OpenBMC PLDM project aims to implement the specifications defined by the Distributed Management Task Force (DMTF), allowing for interoperable management interfaces across different hardware and firmware components.

Features

  • Standardized Messaging: Adheres to the DMTF's PLDM specifications, enabling consistent and interoperable communication between different components.
  • Modularity: Supports multiple PLDM types, including base, FRU,Firmware update, Platform Monitoring and Control, and BIOS Control and Configuration.
  • Extensibility: Easily extendable to support new PLDM types and custom OEM commands.
  • Integration: Seamlessly integrates with other OpenBMC components for comprehensive system management.

Getting Started

Prerequisites

To build and run PLDM, you need the following dependencies:

  • Meson
  • Ninja

Alternatively, source an OpenBMC ARM/x86 SDK.

Building

To build the PLDM project, follow these steps:

meson setup build && meson compile -C build

To run unit tests

The simplest way of running the tests is as described by the meson man page:

meson test -C build

Alternatively, tests can be run in the OpenBMC CI docker container using these steps.

To enable pldm verbosity

pldm daemon accepts a command line argument --verbose or --v or -v to enable the daemon to run in verbose mode. It can be done via adding this option to the environment file that pldm service consumes.

echo 'PLDMD_ARGS="--verbose"' > /etc/default/pldmd
systemctl restart pldmd

To disable pldm verbosity

rm /etc/default/pldmd
systemctl restart pldmd

Documentation

For complete documentation on the functionality and usage of this repository, please refer to the docs folder.