summaryrefslogtreecommitdiffstats
path: root/extensions/openpower-pels/user_data_formats.hpp
diff options
context:
space:
mode:
authorMatt Spinler <spinler@us.ibm.com>2019-10-24 13:03:46 -0500
committerMatt Spinler <spinler@us.ibm.com>2019-11-04 16:18:24 -0600
commitafa857c70ad78fd91f50871005d8a2ef8bf6a59b (patch)
tree647f23105318408ae36b95742bb0d95e88698554 /extensions/openpower-pels/user_data_formats.hpp
parentaa659477fa398f255c5a87207224d59aea15aa34 (diff)
downloadphosphor-logging-afa857c70ad78fd91f50871005d8a2ef8bf6a59b.tar.gz
phosphor-logging-afa857c70ad78fd91f50871005d8a2ef8bf6a59b.zip
PEL: Save AdditionalData in a UserData section
Save the contents of the AdditionalData OpenBMC event log property as JSON in a UserData PEL section. For example, if the AdditionalData property, which is an array of strings, looks like: ["KEY1=VALUE1", "KEY=VALUE2"] Then the data stored as ASCII text in the UserData section is: {"KEY1":"VALUE1","KEY2":"VALUE2"} If one of the keys is "ESEL", then that entry is removed from the UserData output as that contains a full raw PEL from the host sent down as ASCII text. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ia6ffabb39fdb4315ec2152744414e44f7d2ec4aa
Diffstat (limited to 'extensions/openpower-pels/user_data_formats.hpp')
-rw-r--r--extensions/openpower-pels/user_data_formats.hpp19
1 files changed, 19 insertions, 0 deletions
diff --git a/extensions/openpower-pels/user_data_formats.hpp b/extensions/openpower-pels/user_data_formats.hpp
new file mode 100644
index 0000000..53cb5ee
--- /dev/null
+++ b/extensions/openpower-pels/user_data_formats.hpp
@@ -0,0 +1,19 @@
+#pragma once
+
+namespace openpower
+{
+namespace pels
+{
+
+enum class UserDataFormat
+{
+ json = 1
+};
+
+enum class UserDataFormatVersion
+{
+ json = 1
+};
+
+} // namespace pels
+} // namespace openpower
OpenPOWER on IntegriCloud