| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | pel_rules_test.cpp | f1e85e20a1a6e97e27737b5883a8aa6a63c79b22 Fri Nov 01 11:31:31 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Validate the Action Flags field
According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.
In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.
The rules being followed are documented in the PEL readme.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | pel_rules.hpp | f1e85e20a1a6e97e27737b5883a8aa6a63c79b22 Fri Nov 01 11:31:31 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Validate the Action Flags field
According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.
In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.
The rules being followed are documented in the PEL readme.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
|
| H A D | pel_rules.cpp | f1e85e20a1a6e97e27737b5883a8aa6a63c79b22 Fri Nov 01 11:31:31 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Validate the Action Flags field
According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.
In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.
The rules being followed are documented in the PEL readme.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
|
| H A D | pel_types.hpp | diff f1e85e20a1a6e97e27737b5883a8aa6a63c79b22 Fri Nov 01 11:31:31 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Validate the Action Flags field
According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.
In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.
The rules being followed are documented in the PEL readme.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
|
| H A D | user_header.hpp | diff f1e85e20a1a6e97e27737b5883a8aa6a63c79b22 Fri Nov 01 11:31:31 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Validate the Action Flags field
According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.
In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.
The rules being followed are documented in the PEL readme.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
|
| H A D | README.md | diff f1e85e20a1a6e97e27737b5883a8aa6a63c79b22 Fri Nov 01 11:31:31 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Validate the Action Flags field
According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.
In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.
The rules being followed are documented in the PEL readme.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
|
| H A D | user_header.cpp | diff f1e85e20a1a6e97e27737b5883a8aa6a63c79b22 Fri Nov 01 11:31:31 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Validate the Action Flags field
According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.
In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.
The rules being followed are documented in the PEL readme.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
|
| H A D | pel.hpp | diff f1e85e20a1a6e97e27737b5883a8aa6a63c79b22 Fri Nov 01 11:31:31 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Validate the Action Flags field
According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.
In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.
The rules being followed are documented in the PEL readme.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
|
| H A D | pel.cpp | diff f1e85e20a1a6e97e27737b5883a8aa6a63c79b22 Fri Nov 01 11:31:31 CDT 2019 Matt Spinler <spinler@us.ibm.com> PEL: Validate the Action Flags field
According to the PEL spec, the Action Flags and Event Type fields in the
User Header section must be in agreement with the Severity field. So,
when a PEL is being created from an OpenBMC event log, check those
values for correctness and fix them up if required.
In addition, as those fields are optional in the message registry, this
code will also just set these two fields to valid values if they were
left out.
The rules being followed are documented in the PEL readme.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iad88de5080ba79a9ff31f962ef99bfc11994b9ed
|