host-bmc: free instance ID on request registration failure getHostPDR() allocates an instance ID before calling registerRequest() to queue a PLDM request. If registerRequest() fails, the allocated instance ID remains allocated until it expires from the InstanceIdDb. Release the allocated instance ID when registerRequest() fails, matching the cleanup already performed when encode_get_pdr_req() fails. This keeps instance ID handling consistent across error paths and avoids retaining an unneeded instance ID until expiration. No functional change to the successful GetPDR request path. Change-Id: I99f707ef02f096ed1e08d922e18da99b31d43e4f 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.