| commit | b01fb1ccb1751025bc190b805f1d841615e97b76 | [log] [tgz] |
|---|---|---|
| author | Thu Nguyen <thu@os.amperecomputing.com> | Sun May 28 09:16:46 2023 +0700 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Mon Jun 05 12:16:20 2023 +0930 |
| tree | 04fb3e52df4e3474a6ec509f216c7b7ee7381a72 | |
| parent | a8532b543aae9da149108ad9cc549f87345e341f [diff] |
transport: Match on response in pldm_transport_send_recv_msg() pldm_send_recv() does not verify the corrected match of a PLDM response message with the request message by comparing the Instance ID as pldm_recv(). This will cause the PLDM command of the pldmtool receives the response message of the other PLDM command from other services. The pldm_transport_send_recv_msg() which is called by pldm_send_recv() method should check the Instance ID of the response to verify the match. Tested: 1. Run pldmtool while pldmd service continuously polls multiple pldm sensors. 2. The pldmtool should not be failed with PLDM_ERROR_INVALID_LENGTH error. Signed-off-by: Thu Nguyen <thu@os.amperecomputing.com> Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Change-Id: I491db086cf2a0dff1981f2959d1dab936d46d2db
This is a library which deals with the encoding and decoding of PLDM messages. It should be possible to use this library by projects other than OpenBMC, and hence certain constraints apply to it:
Source files are named according to the PLDM Type, for eg base.[h/c], fru.[h/c], etc.
Given a PLDM command "foo", the library will provide the following API: For the Requester function:
encode_foo_req() - encode a foo request decode_foo_resp() - decode a response to foo
For the Responder function:
decode_foo_req() - decode a foo request encode_foo_resp() - encode a response to foo
The library also provides API to pack and unpack PLDM headers.
Need meson and ninja. Alternatively, source an OpenBMC ARM/x86 SDK.
meson setup builddir && ninja -C builddir
The simplest way of running the tests is as described by the meson man page:
meson setup builddir && meson test -C builddir
This will support OEM or vendor-specific functions and semantic information. Following directory structure has to be used:
libpldm |---- include/libpldm | |---- oem/<oem_name>/libpldm | |----<oem based .h files> |---- src | |---- oem/<oem_name> | |----<oem based .c files> |---- tests | |---- oem/<oem_name> | |----<oem based test files>
<oem_name> - This folder must be created with the name of the OEM/vendor in lower case.
Header files & source files having the oem functionality for the libpldm library should be placed under the respective folder hierarchy as mentioned in the above figure. They must be adhering to the rules mentioned under the libpldm section above.
Once the above is done a meson option has to be created in libpldm/meson_options.txt with its mapped compiler flag to enable conditional compilation.
For consistency would recommend using "oem-<oem_name>".
The libpldm/meson.build and the corresponding source file(s) will need to incorporate the logic of adding its mapped compiler flag to allow conditional compilation of the code.
The pldm requester API's are present in src/requester folder and they are intended to provide API's to interact with the desired underlying transport layer to send/receive pldm messages.
NOTE : In the current state, the requester API's in the repository only works with specific transport mechanism & these are going to change in future & probably aren't appropriate to be writing code against.