Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / pldm / 2e2b4823c06508cb38509988b8962543a35ab8aa
commit2e2b4823c06508cb38509988b8962543a35ab8aa[log] [tgz]
authorThang Tran <thuutran@amperecomputing.com>Mon Sep 29 07:27:55 2025 +0000
committerThang Tran <thuutran@amperecomputing.com>Mon Oct 13 06:38:27 2025 +0000
tree1372067a739cd0da56d3ba5292b33b2d081a614f
parent193f9f34c808949357827066543217ec6f45c158 [diff]
oem: ampere: use lg2::commit to log events

Switch to use lg2::commit method to create Redfish events instead
journal logs. The changes of events are mapped as below:
- AmpereEvent -> ReportedSELInfo
- AmpereWarning -> ReportedSELWarning
- AmpereCritical -> ReportedSELCritical
- BIOSFirmwarePanicReason: no change, it still creates journal logs.

Tested:
  1. Turn off/on the Host
     $ipmitool power <off/on>
  2. Check the Redfish events in the schema
     /redfish/v1/Systems/system/LogServices/EventLog/Entries
  3. Host's events are shown

Change-Id: Ib56354a3d7d07265c123918615d0fab7b680e6a7
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
2 files changed
tree: 1372067a739cd0da56d3ba5292b33b2d081a614f
  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.