/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::map<std::string, std::string>& ad) : in AdditionalData() function in openpower::pels::AdditionalData
|
H A D | src.hpp | 93 * this error, along with the AdditionalData property contents from the 97 * @param[in] additionalData - The AdditionalData properties in this event 101 SRC(const message::Entry& regEntry, const AdditionalData& additionalData, in SRC() 110 * this error, along with the AdditionalData property contents from the 114 * @param[in] additionalData - The AdditionalData properties in this event 119 SRC(const message::Entry& regEntry, const AdditionalData& additionalData, 344 * AdditionalData fields. 347 * that entry has a field that says which AdditionalData property 351 * For example, given that AdditionalData is a map of string keys 352 * to string values, find the AdditionalData valu [all...] |
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() 355 // Fill in the last 4 words from the AdditionalData property contents. in SRC() 388 const AdditionalData& ad) in setUserDefinedHexWords() 395 // Save the AdditionalData value corresponding to the first element of in setUserDefinedHexWords() 825 const AdditionalData& additionalData, in addCallouts() 953 const message::Entry& regEntry, const AdditionalData& additionalData, in getRegistryCallouts() 1135 void SRC::addDevicePathCallouts(const AdditionalData& additionalData, in addDevicePathCallouts() 1181 *i2cAddr + " in AdditionalData property"; in addDevicePathCallouts()
|
H A D | manager.cpp | 80 AdditionalData ad{additionalData}; in create() 212 AdditionalData ad; in addPEL() 374 AdditionalData ad{additionalData}; in createPEL() 534 AdditionalData data; in hostReject()
|
H A D | registry.hpp | 307 const AdditionalData& additionalData);
|
H A D | sbe_ffdc_handler.cpp | 74 SbeFFDC::SbeFFDC(const AdditionalData& aData, const PelFFDC& files) : in SbeFFDC()
|
H A D | registry.cpp | 609 const AdditionalData& additionalData) in getCalloutsUsingAD() 895 const AdditionalData& additionalData) in getCallouts()
|
/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() 252 AdditionalData ad{adData}; in TEST() 271 AdditionalData ad; in TEST() 301 AdditionalData ad; in TEST() 329 AdditionalData ad{adData}; in TEST() 346 AdditionalData ad{adData}; in TEST() 363 AdditionalData ad{adData}; in TEST()
|
H A D | src_test.cpp | 206 AdditionalData ad{adData}; in TEST_F() 267 AdditionalData ad{adData}; in TEST_F() 312 AdditionalData ad{adData}; in TEST_F() 335 AdditionalData ad{adData}; in TEST_F() 387 AdditionalData ad{adData}; in TEST_F() 428 AdditionalData ad{adData}; in TEST_F() 527 AdditionalData ad; in TEST_F() 572 AdditionalData ad; in TEST_F() 610 AdditionalData ad; in TEST_F() 675 // CALLOUT_INVENTORY_PATH AdditionalData entr [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() 741 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() [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() 241 AdditionalData ad{data}; in TEST_F() 366 AdditionalData additionalData{ad}; in TEST_F() 412 AdditionalData additionalData{ad}; in TEST_F() 754 AdditionalData ad{additionalData}; in TEST_F() 869 AdditionalData ad{data}; in TEST_F() 923 AdditionalData ad{data}; in TEST_F() 994 AdditionalData ad; in TEST_F() 1074 AdditionalData ad; in TEST_F() 1151 AdditionalData ad{data}; 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 | 55 # "AdditionalData": [ 97 Check eSEL AdditionalData 98 [Documentation] Generate eSEL log and verify AdditionalData is 108 # "AdditionalData": [], 113 Should Not Be Empty ${resp.json()["data"]["AdditionalData"]}
|
/openbmc/phosphor-host-ipmid/ |
H A D | selutility.hpp | 39 using AdditionalData = std::map<std::string, std::string>; typedef 41 std::variant<Resolved, Id, Timestamp, Message, AdditionalData>;
|
H A D | selutility.cpp | 84 const AdditionalData& data, GetSELEntryResponse& record) in constructOEMSEL() 110 const AdditionalData& data, const entryDataMap&, in constructSEL() 217 const auto& addData = std::get<AdditionalData>(iterId->second); in prepareSELEntry() 239 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 225 desired. On the BMC, the source of these words is the AdditionalData fields in 227 specify which AdditionalData property field to get the data from, and also to 325 AdditionalData property field. Callouts will be added to the PEL in the order 441 #### Callouts example based on an AdditionalData field 485 AdditionalData field. When PROC_NUM was 0, the FRU at P1-C5 was called out. When 490 the AdditionalData field, one can use CalloutsWhenNoADMatch. In the following 559 AdditionalData property. The code will then look up the location code for that
|
/openbmc/phosphor-logging/ |
H A D | README.md | 57 based on text in the AdditionalData property. A callout is a link to the 142 the event. It shows up in the AdditionalData property in the 168 In the above example, the AdditionalData property would look like: 226 - AdditionalData: The `AdditionalData` property for the 251 (AdditionalData) as in the corresponding metadata YAML file.
|