| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | additional_data.hpp | 25 class AdditionalData class
28 AdditionalData() = default;
29 ~AdditionalData() = default;
30 AdditionalData(const AdditionalData&) = default;
31 AdditionalData& operator=(const AdditionalData&) = default;
32 AdditionalData(AdditionalData&&) = default;
33 AdditionalData& operator=(AdditionalData&&) = default;
41 explicit AdditionalData(const std::vector<std::string>& ad) in AdditionalData() function in openpower::pels::AdditionalData
|
| H A D | src.hpp | 101 SRC(const message::Entry& regEntry, const AdditionalData& additionalData, in SRC()
119 SRC(const message::Entry& regEntry, const AdditionalData& additionalData,
359 const AdditionalData& additionalData);
460 const AdditionalData& additionalData,
488 const message::Entry& regEntry, const AdditionalData& additionalData,
547 void addDevicePathCallouts(const AdditionalData& additionalData,
|
| H A D | pel.hpp | 114 const AdditionalData& additionalData, const PelFFDC& ffdcFiles,
474 std::unique_ptr<UserData> makeADUserDataSection(const AdditionalData& ad);
490 const AdditionalData& ad, const DataInterfaceBase& dataIface,
|
| H A D | event_logger.hpp | 45 AdditionalData>;
75 phosphor::logging::Entry::Level severity, const AdditionalData& ad) in log()
|
| H A D | sbe_ffdc_handler.hpp | 126 SbeFFDC(const AdditionalData& data, const PelFFDC& files);
|
| H A D | user_header.hpp | 53 const AdditionalData& additionalData,
|
| H A D | pel.cpp | 64 const AdditionalData& additionalData, const PelFFDC& ffdcFilesIn, in PEL()
559 const AdditionalData additionalData; in updateSysInfoInExtendedUserDataSection()
812 std::unique_ptr<UserData> makeADUserDataSection(const AdditionalData& ad) in makeADUserDataSection()
917 const AdditionalData& ad, const DataInterfaceBase& dataIface, in makeSysInfoUserDataSection()
|
| H A D | README.md | 25 keywords in the AdditionalData property of the event log.
27 ### AdditionalData keywords
215 - The AdditionalData property contents
217 - If the AdditionalData property in the OpenBMC event log has anything in it,
239 ### Passing callouts in with the AdditionalData property
242 AdditionalData event log property. They are:
297 type or on any AdditionalData item.
303 AdditionalData entry, then that will also be a key.
311 also contains one of aforementioned CALLOUT keys in the AdditionalData property,
|
| H A D | src.cpp | 308 SRC::SRC(const message::Entry& regEntry, const AdditionalData& additionalData, in SRC()
388 const AdditionalData& ad) in setUserDefinedHexWords()
825 const AdditionalData& additionalData, in addCallouts()
942 const message::Entry& regEntry, const AdditionalData& additionalData, in getRegistryCallouts()
1101 void SRC::addDevicePathCallouts(const AdditionalData& additionalData, in addDevicePathCallouts()
|
| H A D | manager.cpp | 80 AdditionalData ad{additionalData}; in create()
212 AdditionalData ad; in addPEL()
369 AdditionalData ad{additionalData}; in createPEL()
529 AdditionalData data; in hostReject()
|
| H A D | registry.hpp | 307 const AdditionalData& additionalData);
|
| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | user_header_test.cpp | 115 AdditionalData ad; in TEST()
156 AdditionalData ad; in TEST()
206 AdditionalData ad; in TEST()
228 AdditionalData ad; in TEST()
251 AdditionalData ad{adData}; in TEST()
270 AdditionalData ad; in TEST()
300 AdditionalData ad; in TEST()
328 AdditionalData ad{adData}; in TEST()
345 AdditionalData ad{adData}; in TEST()
362 AdditionalData ad{adData}; in TEST()
|
| H A D | src_test.cpp | 203 AdditionalData ad{adData}; in TEST_F()
264 AdditionalData ad{adData}; in TEST_F()
306 AdditionalData ad{adData}; in TEST_F()
328 AdditionalData ad{adData}; in TEST_F()
518 AdditionalData ad; in TEST_F()
563 AdditionalData ad; in TEST_F()
601 AdditionalData ad; in TEST_F()
749 AdditionalData ad; in TEST_F()
1029 AdditionalData ad; in TEST_F()
1215 AdditionalData ad; in TEST_F()
[all …]
|
| H A D | additional_data_test.cpp | 26 AdditionalData ad{data}; in TEST()
53 AdditionalData ad; in TEST()
|
| H A D | registry_test.cpp | 508 AdditionalData ad; in TEST_F()
554 AdditionalData ad; in TEST_F()
594 AdditionalData ad; in TEST_F()
692 AdditionalData ad{adData}; in TEST_F()
727 AdditionalData ad{adData}; in TEST_F()
787 AdditionalData ad{adData}; in TEST_F()
843 AdditionalData ad; in TEST_F()
938 AdditionalData ad; in TEST_F()
1035 AdditionalData ad; in TEST_F()
1107 AdditionalData ad; in TEST_F()
[all …]
|
| H A D | event_logger_test.cpp | 40 AdditionalData d; in create()
76 AdditionalData ad; in TEST()
|
| H A D | pel_test.cpp | 166 AdditionalData ad{data}; in TEST_F()
244 AdditionalData ad{data}; in TEST_F()
871 AdditionalData ad{data}; in TEST_F()
925 AdditionalData ad{data}; in TEST_F()
996 AdditionalData ad; in TEST_F()
1076 AdditionalData ad; in TEST_F()
1153 AdditionalData ad{data}; in TEST_F()
1328 AdditionalData ad; in TEST_F()
1404 AdditionalData ad; in TEST_F()
1447 AdditionalData ad; in TEST_F()
[all …]
|
| /openbmc/openbmc-test-automation/redfish/systems/eventlog/ |
| H A D | test_event_association.robot | 35 Create Test Error Callout And Verify AdditionalData
36 [Documentation] Create Test Error Callout And Verify AdditionalData.
41 # "AdditionalData": [
51 ... ${resp.json()["data"]["AdditionalData"]} CALLOUT_DEVICE_PATH_TEST=${target_device_path}
52 List Should Contain Value ${resp.json()["data"]["AdditionalData"]} DEV_ADDR=0x0DEADEAD
84 # "AdditionalData": [
121 # "AdditionalData": [
145 # "AdditionalData": [
231 # "AdditionalData": [
|
| H A D | test_esel.robot | 54 # "AdditionalData": [
98 Check eSEL AdditionalData
99 [Documentation] Generate eSEL log and verify AdditionalData is
109 # "AdditionalData": [],
114 Should Not Be Empty ${resp.json()["data"]["AdditionalData"]}
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | Create.interface.yaml | 19 - name: AdditionalData
22 The AdditionalData property of the event entry. e.g.:
55 - name: AdditionalData
58 The AdditionalData property of the event entry. e.g.:
|
| H A D | Event.interface.yaml | 27 - name: AdditionalData
|
| /openbmc/phosphor-host-ipmid/ |
| H A D | selutility.hpp | 39 using AdditionalData = std::vector<std::string>; typedef
41 std::variant<Resolved, Id, Timestamp, Message, AdditionalData>;
|
| H A D | selutility.cpp | 72 additionalDataMap parseAdditionalData(const AdditionalData& data) in parseAdditionalData()
240 const auto& addData = std::get<AdditionalData>(iterId->second); in prepareSELEntry()
|
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/ |
| H A D | README.md | 59 the time of PEL creation using the 'PEL_SUBSYSTEM' AdditionalData field. In this
224 desired. On the BMC, the source of these words is the AdditionalData fields in
226 specify which AdditionalData property field to get the data from, and also to
324 AdditionalData property field. Callouts will be added to the PEL in the order
440 #### Callouts example based on an AdditionalData field
484 AdditionalData field. When PROC_NUM was 0, the FRU at P1-C5 was called out. When
489 the AdditionalData field, one can use CalloutsWhenNoADMatch. In the following
558 AdditionalData property. The code will then look up the location code for that
|
| /openbmc/phosphor-dbus-interfaces/yaml/org/open_power/Logging/ |
| H A D | PEL.interface.yaml | 79 - name: AdditionalData
82 The AdditionalData property of the event entry. e.g.:
|