summaryrefslogtreecommitdiffstats
path: root/extensions/openpower-pels/registry
Commit message (Collapse)AuthorAgeFilesLines
* PEL: New event log when receiving bad host PELMatt Spinler2020-02-141-0/+37
| | | | | | | | | | | | Create a new event log/PEL when a PEL comes in from the host but it isn't valid. The PEL subsystem used is 'platform firmware' because the code won't know which specific host subsystem it came from. The severity is unrecoverable as opposed to informational to make it easier to notice. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I933e5c82f1ef755c6266604fbdec6d0c1fe5b784
* PEL: Create error log for 'bad PEL'Matt Spinler2020-02-141-0/+28
| | | | | | | | | Create an event log (and a PEL) for the case when the host rejects a PEL because it is malformed. This requires a new message registry entry for the error. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ibd52921b5d6020f98b457b9ee0b3bb4f0b95e707
* PEL: Fix message registry schema typoMatt Spinler2019-12-111-1/+1
| | | | Change-Id: Ic20d6560a79dc8cc871ebc1ab64ce5aefc2ccfe6
* PEL: Validate the message registry during CIMatt Spinler2019-11-181-0/+3
| | | | | | | | | CI will run any files called run-ci.sh it finds in a repo, so add a script of that name to run process_registry.py against the message registry to check it for errors. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I35da7c1454696b90ec88b3545992414160ae920b
* PEL: Add the 'Common' errors to the registryMatt Spinler2019-11-151-0/+131
| | | | | | | | | | | | | | | Add the xyz.openbmc_project.Common.Error.* errors from xyz/openbmc_project/Common.errors.yaml file in the phosphor-dbus-interfaces repository. It is possible that errors defined in these YAML files never have event logs created out of them, but instead are intended to just be returned on failed D-Bus operations, such as a method failure. Aside from searching the whole OpenBMC code base there is no way to know, so just define PELs for all of them to be safe. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I00ce1e9423c2b260f78d2d3d0aa8a495c3b13504
* PEL: Registry: Make "Action Flags" optionalMatt Spinler2019-11-122-3/+10
| | | | | | | | | | | | | | | The Action Flags bits in the PEL need to be in agreement with other PEL fields, such as if the severity is informational then the 'report' flag cannot be on. In fact, for most logs all of these flags can be deduced from the other PEL fields. So, to avoid the case of the action flags in the registry not matching the other PEL fields, make them optional and the BMC code will set them appropriately. And when they are specified, the BMC code will still run through the same code to ensure everything is in agreement. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I5bea83d01846d7a2d3307666e6d0758a99229e3f
* PEL: Check duplicate reason codes in registryMatt Spinler2019-10-251-0/+19
| | | | | | | | | Reason codes must be unique for every error until there is a specific reason for them not to be, so check for that while validating the message registry JSON file. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I74e0e24e1f129ebf94d25aaf5200b30b256b1307
* PEL: Script to validate message registry JSONMatt Spinler2019-10-251-0/+148
| | | | | | | | This script will check the JSON against the schema, as well as do a few other checks that can't be encoded into a schema. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I97c0fc0f69baac3c076b557b67e47ce8abfccf36
* PEL: Add message registry READMEMatt Spinler2019-10-252-0/+241
| | | | | | | | | | | This README describes the message registry in an easier to read way than what is buried in the JSON schema. The commit also provides a file to document which component IDs are used by which repositories/applications. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ibf1109e0a1fb6fff872cfa91d79c007ecf5527b0
* PEL: Add message registry JSON schemaMatt Spinler2019-10-252-0/+394
| | | | | | | | | | | | | | | | | | | | | | The message registry is JSON data that will aid in converting OpenBMC event logs into IBM's Platform Event Log (PEL) format. PELs have more fields than event logs, many with specific IBM defined values, that need to be able to be looked up for an OpenBMC event log so the PEL can be filled in. In addition to aiding in creating PELs, it also contains information to aid in parsing PELs. This schema defines how that JSON will look, and this commit also contains an example registry file. A script will be added in the future to validate the registry JSON against the schema during a bitbake build. Until there is a need, the message registry will be contained in a single JSON file. If there is a need, it can be split up along some predetermined rules in the future. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I98620b263bd1faff27e36da7a0c101a982b58057
* PEL: Install an empty PEL message registryMatt Spinler2019-10-251-0/+6
This will eventually contain the information to create PELs out of OpenBMC event logs. It is installed into /usr/share/phosphor-logging/pels. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Iaf67881890a47f605af3ae69b54f186b63915ca6
OpenPOWER on IntegriCloud