| commit | 463b65f4e622fc1305ed538fb8dd04faada98c51 | [log] [tgz] |
|---|---|---|
| author | Jinliang Wang <jinliangw@google.com> | Tue Oct 07 10:35:37 2025 -0700 |
| committer | Jinliang Wang <jinliangw@google.com> | Tue Oct 07 10:39:35 2025 -0700 |
| tree | dc0c1fbfc2476376f62df1d7495da4686670b468 | |
| parent | c00d5bf65f7ca3df557be8e2f704e5a0ef62321f [diff] |
Revert "platform-mc: Add structured logging for threshold events" This reverts commit 79931b6720138881c0b710f986b16145093289e3. gbmc doesn't suport structured logging API and we don't use this feature Google-Bug-Id: 442010239 Tested: presubmit-build Change-Id: Id568b50e48b429018c3fcf9790179d1644a2e460 Signed-off-by: Jinliang Wang <jinliangw@google.com>
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.
To build and run PLDM, you need the following dependencies:
MesonNinjaAlternatively, source an OpenBMC ARM/x86 SDK.
To build the PLDM project, follow these steps:
meson setup build && meson compile -C build
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.
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
rm /etc/default/pldmd systemctl restart pldmd
For complete documentation on the functionality and usage of this repository, please refer to the docs folder.