summaryrefslogtreecommitdiffstats
path: root/extensions/openpower-pels/manager.hpp
diff options
context:
space:
mode:
authorMatt Spinler <spinler@us.ibm.com>2019-08-27 13:56:05 -0500
committerMatt Spinler <spinler@us.ibm.com>2019-10-01 12:52:33 -0500
commit835a86938f3cf59fbdcd25835b48e6cdb1e6552b (patch)
treeeca6865e34aa490abfe231b72c8b7f2492a88908 /extensions/openpower-pels/manager.hpp
parent09d6400fb70d5324c0ed026d1084fc51cb495216 (diff)
downloadphosphor-logging-835a86938f3cf59fbdcd25835b48e6cdb1e6552b.tar.gz
phosphor-logging-835a86938f3cf59fbdcd25835b48e6cdb1e6552b.zip
PEL: Support for going between PELs & registry
Add tables that allow one to go between how a PEL field actually shows up in the PEL (raw bytes) and how it shows up in the message registry (a string enumeration). The tables also have a column to show a string description of that value that can be used by the parser, though for now those descriptions are all left at "TODO". There only needs to be a table for a PEL field when there is a corresponding message registry field that is a string enumeration, so that when code looks up an error in the message registry it knows what to fill in the PEL with. Also provide APIs to look up a row in the table by either the PEL value or the message registry value. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Iac849bcd2b0449a8d03fac7eb067484e91d28259
Diffstat (limited to 'extensions/openpower-pels/manager.hpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud