Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / pldm / HEAD
commit0b06dd891c42103a4555a0376e7a47b604f01ca9[log] [tgz]
authorAditya Kurdunkar <adityakurdunkar2@gmail.com>Thu Nov 27 10:18:01 2025 +0530
committerDeepak Kodihalli <deepak.kodihalli.83@gmail.com>Mon Dec 15 09:37:45 2025 +0000
tree24346782d452fbdc0a5d7771b3b33d78508becc6
parent28ba36aa9ecc3b4e8f2c2f8b2821dd8ec8c83d78 [diff]
oem-nvidia: Add support for legacy CPER event handling

Add OEM support to handle legacy CPER events using event class 0xFA for
existing NVIDIA platforms.

Prior to DSP0248 V1.3.0, NVIDIA used OEM event class 0xFA to report CPER
events. The spec later standardized CPER events as class 0x07
(PLDM_CPER_EVENT). This change maintains backwards compatibility by
registering handlers for both the legacy 0xFA and the standardized 0x07
event classes.

This ensures continued support for NVIDIA platforms using older firmware
while being compatible with the current PLDM specification.

Tested.

This patch was tested on Nvidia GB200 Platform on Grace CPU Terminus.
The CPER payload was generated in /var/cper

'''
$ ls /var/cper/*
/var/cper/cper-lSaBc
'''

Change-Id: Ia0bb6c78b6abdc2c9ac2ea9249f180177d4aabcf
Signed-off-by: Aditya Kurdunkar <adityakurdunkar2@gmail.com>
4 files changed
tree: 24346782d452fbdc0a5d7771b3b33d78508becc6
  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.