platform-mc: stop multipart PDR processing on TRANSFER_END PLDM_PLATFORM_TRANSFER_END indicates that the complete PDR record has been received. After moving the assembled record into terminus->pdrs, continuing the multipart transfer loop is unnecessary and can leave a potential post-move access path for receivedPdr. Break out of the loop immediately after handling TRANSFER_END to make the completion condition explicit, simplify control flow, and resolve the cppcheck accessMoved warning. No functional change is intended for valid transfers. Change-Id: I2f5cb57757dcc69d3d622780f17126777d4d5928 Signed-off-by: Meghana Vangapandu <meghanav@ami.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.