| #
7e374fb4 |
| 07-Apr-2022 |
Chris Cain <cjcain@us.ibm.com> |
Ignore PLDM message if status objects not created
The OCC status objects are not created until after the host@0-on file
has been removed. This now delays when the objects are created.
This introduce
Ignore PLDM message if status objects not created
The OCC status objects are not created until after the host@0-on file
has been removed. This now delays when the objects are created.
This introduced a window where the host notified occ-control that the
OCCs were running (via PLDM) before the status objects were created
which led to a segfault.
This commit will verify the status object exists when getting the PLDM
callback.
Verified on Rainier
Change-Id: I72404d1b5d89c5259cc9f857c8087096644ef318
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
show more ...
|
| #
1d69e192 |
| 21-Mar-2019 |
Alexander Filippov <a.filippov@yadro.com> |
Add support for sensorName field in yaml
We want to have ability to specify the human readable names for the OCC
sensors. E.g. `CPU0_OCC` instead of `occ_4_0050`.
This commit allows to specify a `s
Add support for sensorName field in yaml
We want to have ability to specify the human readable names for the OCC
sensors. E.g. `CPU0_OCC` instead of `occ_4_0050`.
This commit allows to specify a `sensorName` field in the YAML config
for each sensor, and this name will be used in the sensor object DBus
path. If the field is not specified, previous behavior will be used.
Tested: the command `busctl tree org.open_power.OCC.Control --list` must
show specified names.
Change-Id: I2f05f7bf44120554ea07b9ee0aac9cfbd33ac376
Signed-off-by: Alexander Filippov <a.filippov@yadro.com>
show more ...
|