History log of /openbmc/phosphor-logging/test/openpower-pels/severity_test.cpp (Results 1 – 3 of 3)
Revision Date Author Comments
# 8b81ec0e 12-Jul-2022 Matt Spinler <spinler@us.ibm.com>

PEL: Update D-Bus event sev based on PEL severity

Put in checks to ensure the D-Bus event log severity agrees with the
final PEL severity for PELs created by the BMC. The D-bus property is
what is

PEL: Update D-Bus event sev based on PEL severity

Put in checks to ensure the D-Bus event log severity agrees with the
final PEL severity for PELs created by the BMC. The D-bus property is
what is used in the Redfish event log, and we want to avoid cases like
having a Critical event log for an informational PEL.

This could happen in the case where the PEL message registry entry for
the event has a hardcoded or manufacturing specific severity value that
is different than the severity the D-Bus event log is first created
with.

This commit ensures that:
* If the PEL is nonError/recovered, the D-Bus severity is one of the
non error ones.
* If the PEL isn't nonError/recovered, then the D-Bus severity also
isn't.
* If the PEL is critical, the D-Bus severity is also critical.

It doesn't try to update the D-Bus severity for every PEL severity
because there isn't a one to one mapping - e.g. Notice, Debug, and
Informational D-Bus severities all map to a PEL severity of
nonError(informational).

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I6b0006034090e6d8e33e9f8b136ae50cce489f6e

show more ...


# 97f7abcf 06-Nov-2019 Matt Spinler <spinler@us.ibm.com>

PEL: Add license prologue to test source files

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I67c62ab5ac6e69ad0a84937834581f9a280a9167


# 8c686cca 20-Sep-2019 Matt Spinler <spinler@us.ibm.com>

PEL: OpenBMC event log sev to PEL sev helper

Add a function to map the OpenBMC event log severity values to PEL
severity values.

When creating a PEL from an OpenBMC event log, the event log will ha

PEL: OpenBMC event log sev to PEL sev helper

Add a function to map the OpenBMC event log severity values to PEL
severity values.

When creating a PEL from an OpenBMC event log, the event log will have
its own severity property, and if the PEL message registry entry for
that error doesn't supply its own severity (it's optional), use this
function to come up with the PEL severity value to use.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I66aa001265d8acadb165de874e4ade03a8e28007

show more ...