Google GitGoogle Git
Sign in
gbmc/pldm/db7aa157bee691a97de41d409c3d29484bb80e11
commit
db7aa157bee691a97de41d409c3d29484bb80e11
[log]
author
Alexander Hansen <alexander.hansen@9elements.com>
Tue Jul 14 11:30:25 2026 +0200
committer
Alexander Hansen <alexander.hansen@9elements.com>
Wed Jul 15 11:36:05 2026 +0200
tree
a82470c4725efd71341628a1ecd797e63622b727
parent
cf3ea39983d4bcf139c3ac25173ebebb9f1d72b2 [diff]
handleRequest use start_lifetime_as consistently

GCC16 returned an error w.r.t. potentially uninitialized data in
`relayedResponseMsg->payload[0]` and replacing that with
start_lifetime_as does not result in compilation error.

```
../fw-update/aggregate_update_manager.cpp: In member function ‘virtual pldm::Response pldm::fw_update::AggregateUpdateManager::handleRequest(mctp_eid_t, uint8_t, const pldm_msg*, size_t)’:
../fw-update/aggregate_update_manager.cpp:25:42: error: ‘*(pldm_msg*)MEM[(struct vector *)response_8(D)].D.366301._M_impl.D.365600._M_start.pldm_msg::payload[0]’ may be used uninitialized [-Werror=maybe-uninitialized]
   25 |         if (relayedResponseMsg->payload[0] != PLDM_FWUP_COMMAND_NOT_EXPECTED)
      |             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
```

Also improves consistency with how the response is handled.

Tested: Inspection only, relying on review since i don't have pldm
devices.

Change-Id: Ic6df829957a239844b42ae97ded2d6400372ccf0
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
1 file changed
tree: a82470c4725efd71341628a1ecd797e63622b727
  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.