| commit | a2ddc96eec6d1bc2468b76ba3a606db55e6c0ea8 | [log] [tgz] |
|---|---|---|
| author | Sunny Srivastava <sunnsr25@in.ibm.com> | Wed Jun 29 08:53:16 2022 -0500 |
| committer | Santosh Puranik <santosh.puranik@in.ibm.com> | Tue Dec 06 23:33:31 2022 +0530 |
| tree | 1c3873da496959b62bb0b24a6753a6924790b2f2 | |
| parent | fdf9ff2a573870aacbec4600b8401dca0cc93c2c [diff] |
Async request to create PEL To avoid any deadlocks between phosphor-logging and vpd-manager service a wrapper around request to create PEL is created which enables vpd-manager to make async requests to create PEL. It also implements a new exception type to throw any GPIO related exception. This was required to throw specific exception. Test: Scenario 1: While vpd-manager logs a pel with call out to an inventory item. It should be checked that both the services do not enter into a deadlock situation. Scenario 2: Any third process is requesting to log PEL with call out to an inventory item in a loop. In the mean time vpd-manager also requests to log a PEL with or without call out to inventory item. All the pels should be logged correctly in the system. No deadlock should appear. Signed-off-by: Sunny Srivastava <sunnsr25@in.ibm.com> Change-Id: I0efaf6918e679ca94808fc70d747c843a50eaf78
This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both OpenPower VPD and IPZ VPD formats are structured binaries that consist of records and keywords. A record is a collection of multiple keywords. More information about the format can be found here.
The repository consists of two distinct applications, which are:
This is a build-time YAML driven application that parses the OpenPower VPD format and uses the YAML configuration (see extra-properties-example.yaml and writefru.yaml) to determine:
The application instance must be passed in the file path to the VPD (this can, for example, be a sysfs path exposed by the EEPROM device driver) and also the D-Bus object path(s) that EEPROM data needs to be published under.
This parser is can be built by passing in the --enable-ibm-parser configure option. This parser differs from the OpenPower VPD parser in the following ways:
# and are > 255 bytes in length).Making the application runtime JSON driven allows us to support multiple systems (with different FRU configurations) to be supported in a single code image as well as making the application more flexible for future improvements.