Home
last modified time | relevance | path

Searched refs:PEL (Results 1 – 25 of 40) sorted by relevance

12

/openbmc/openbmc-test-automation/openpower/pel/
H A Dtest_bmc_pel.robot2 Documentation This suite tests Platform Event Log (PEL) functionality of OpenBMC.
27 Create Test PEL Log And Verify
28 [Documentation] Create PEL log using busctl command and verify via peltool.
32 Create Test PEL Log
33 ${pel_id}= Get PEL Log Via BMC CLI
34 Should Not Be Empty ${pel_id} msg=System PEL log entry is empty.
37 Verify PEL Log Details
38 [Documentation] Verify PEL log details via peltool.
44 Create Test PEL Log
71 # Verify if "CompID" and "SRC" fields of PEL has alphanumeric value.
[all …]
/openbmc/phosphor-logging/extensions/openpower-pels/
H A Dpel.hpp63 class PEL class
66 PEL() = delete;
67 ~PEL() = default;
68 PEL(const PEL&) = delete;
69 PEL& operator=(const PEL&) = delete;
70 PEL(PEL&&) = delete;
71 PEL& operator=(PEL&&) = delete;
85 explicit PEL(std::vector<uint8_t>& data);
95 PEL(std::vector<uint8_t>& data, uint32_t obmcLogID);
112 PEL(const openpower::pels::message::Entry& entry, uint32_t obmcLogID,
H A Dpel.cpp62 PEL::PEL(const message::Entry& regEntry, uint32_t obmcLogID, uint64_t timestamp, in PEL() function in openpower::pels::PEL
213 PEL::PEL(std::vector<uint8_t>& data) : PEL(data, 0) {} in PEL() function in openpower::pels::PEL
215 PEL::PEL(std::vector<uint8_t>& data, uint32_t obmcLogID) in PEL() function in openpower::pels::PEL
220 void PEL::populateFromRawData(std::vector<uint8_t>& data, uint32_t obmcLogID) in populateFromRawData()
239 bool PEL::valid() const in valid()
260 void PEL::setCommitTime() in setCommitTime()
266 void PEL::assignID() in assignID()
271 void PEL::flatten(std::vector<uint8_t>& pelBuffer) const in flatten()
289 std::vector<uint8_t> PEL::data() const in data()
296 size_t PEL::size() const in size()
[all …]
H A DREADME.md1 # OpenPower Platform Event Log (PEL) extension
4 to point to the raw PEL to use in the OpenBMC event, and then that will be used
11 - [The PEL Message Registry](#the-pel-message-registry)
15 - [PEL Retention](#pel-retention)
16 - [Adding python3 modules for PEL UserData and SRC parsing](#adding-python3-modules-for-pel-userdat…
19 - [PEL Archiving](#pel-archiving)
22 ## Passing PEL related data within an OpenBMC event log
24 An error log creator can pass in data that is relevant to a PEL by using certain
31 This keyword is used to point to an existing PEL in a binary file that should be
35 RAWPEL=<path to PEL File>
[all …]
H A Dmanager.hpp28 sdbusplus::org::open_power::Logging::server::PEL>;
247 std::string getResolution(const openpower::pels::PEL& pel) const;
254 std::string getEventId(const openpower::pels::PEL& pel) const;
286 void updateProgressSRC(std::unique_ptr<openpower::pels::PEL>& pel) const;
415 void checkPelAndQuiesce(std::unique_ptr<openpower::pels::PEL>& pel);
425 void updateEventId(std::unique_ptr<openpower::pels::PEL>& pel);
457 bool updateResolution(const openpower::pels::PEL& pel);
466 void updateDBusSeverity(const openpower::pels::PEL& pel);
506 openpower::pels::PEL& pel);
H A Drepository.hpp169 void add(std::unique_ptr<PEL>& pel);
227 using ForEachFunc = std::function<bool(const PEL&)>;
247 using AddCallback = std::function<void(const PEL&)>;
454 void archivePEL(const PEL& pel);
456 using PELUpdateFunc = std::function<bool(PEL&)>;
492 void processAddCallbacks(const PEL& pel) const;
515 void write(const PEL& pel, const std::filesystem::path& path);
H A Dservice_indicators.hpp38 virtual void activate(const PEL& pel) = 0;
92 void activate(const PEL& pel) override;
120 bool ignore(const PEL& pel) const;
H A Drepository.cpp95 PEL pel{data}; in restore()
169 void Repository::add(std::unique_ptr<PEL>& pel) in add()
204 void Repository::write(const PEL& pel, const fs::path& path) in write()
336 PEL pel{data}; in for_each()
353 void Repository::processAddCallbacks(const PEL& pel) const in processAddCallbacks()
407 PELUpdateFunc func = [state](PEL& pel) { in setPELHostTransState()
433 PELUpdateFunc func = [state](PEL& pel) { in setPELHMCTransState()
458 PEL pel{data}; in updatePEL()
778 void Repository::archivePEL(const PEL& pel) in archivePEL()
H A Dhost_notifier.hpp172 void newLogCallback(const PEL& pel);
194 bool addPELToQueue(const PEL& pel);
H A Dmanager.cpp141 auto pel = std::make_unique<openpower::pels::PEL>(pelData, obmcLogID); in addPEL()
399 auto pel = std::make_unique<openpower::pels::PEL>( in createPEL()
699 void Manager::checkPelAndQuiesce(std::unique_ptr<openpower::pels::PEL>& pel) in checkPelAndQuiesce()
737 std::string Manager::getEventId(const openpower::pels::PEL& pel) const in getEventId()
762 void Manager::updateEventId(std::unique_ptr<openpower::pels::PEL>& pel) in updateEventId()
784 std::string Manager::getResolution(const openpower::pels::PEL& pel) const in getResolution()
850 bool Manager::updateResolution(const openpower::pels::PEL& pel) in updateResolution()
871 void Manager::updateDBusSeverity(const openpower::pels::PEL& pel) in updateDBusSeverity()
1013 std::unique_ptr<openpower::pels::PEL>& pel) const in updateProgressSRC()
1059 openpower::pels::PEL& pel) in clearPowerThermalDeconfigFlag()
[all …]
H A Dservice_indicators.cpp35 bool LightPath::ignore(const PEL& pel) const in ignore()
53 void LightPath::activate(const PEL& pel) in activate()
/openbmc/phosphor-logging/test/openpower-pels/
H A Drepository_test.cpp73 auto pel = std::make_unique<PEL>(data); in TEST_F()
102 auto pel = std::make_unique<PEL>(data, 1); in TEST_F()
132 auto pel = std::make_unique<PEL>(data, 1); in TEST_F()
139 auto pel = std::make_unique<PEL>(data, 2); in TEST_F()
201 auto pel = std::make_unique<PEL>(data); in TEST_F()
218 auto pel = std::make_unique<PEL>(data); in TEST_F()
221 pel = std::make_unique<PEL>(data); in TEST_F()
228 Repository::ForEachFunc f1 = [&ids](const PEL& pel) { in TEST_F()
238 Repository::ForEachFunc f2 = [&ids](const PEL& pel) { in TEST_F()
253 Repository::AddCallback ac = [&added](const PEL& pel) { in TEST_F()
[all …]
H A Dpel_test.cpp63 auto pel = std::make_unique<PEL>(data); in TEST_F()
81 auto pel = std::make_unique<PEL>(data); in TEST_F()
91 auto newPel = std::make_unique<PEL>(newData); in TEST_F()
98 auto pel = std::make_unique<PEL>(data); in TEST_F()
108 auto newPel = std::make_unique<PEL>(newData); in TEST_F()
115 auto pel = std::make_unique<PEL>(data, 0x42); in TEST_F()
128 auto pel = std::make_unique<PEL>(data); in TEST_F()
137 pel = std::make_unique<PEL>(data); in TEST_F()
147 auto pel = std::make_unique<PEL>(data); in TEST_F()
171 PEL pel{regEntry, 42, timestamp, phosphor::logging::Entry::Level::Error, in TEST_F()
[all …]
H A Dservice_indicators_test.cpp49 PEL pel{data}; in TEST()
283 PEL pel{data}; in TEST()
309 PEL pel{data}; in TEST()
326 PEL pel{data}; in TEST()
348 PEL pel{data}; in TEST()
367 PEL pel{data}; in TEST()
386 PEL pel{data}; in TEST()
H A Dhost_notifier_test.cpp84 std::unique_ptr<PEL> makePEL(uint16_t actionFlagsMask = 0) in makePEL()
92 auto pel = std::make_unique<PEL>(data, obmcID++); in makePEL()
312 PEL pelFromRepo{*data}; in TEST_F()
596 PEL pelFromRepo1{*data}; in TEST_F()
601 PEL pelFromRepo2{*data}; in TEST_F()
645 PEL pelFromRepo{*data}; in TEST_F()
725 PEL pelFromRepo{*data}; in TEST_F()
H A Dpel_manager_test.cpp135 // a PEL saved in the repository.
149 // Create a PEL, write it to a file, and pass that filename into in TEST_F()
166 // Find the file in the PEL repository directory in TEST_F()
192 // Create a PEL, write it to a file, and pass that filename into in TEST_F()
212 // Run the event loop to log the bad PEL event in TEST_F()
216 PEL invalidPEL{data}; in TEST_F()
224 // Check that the bad PEL data was saved to a file. in TEST_F()
229 // Test that the message registry can be used to build a PEL.
297 // Create the event log to create the PEL from. in TEST_F()
302 // Ensure a PEL wa in TEST_F()
[all...]
/openbmc/phosphor-dbus-interfaces/gen/org/open_power/Logging/PEL/
H A Dmeson.build4 sdbusplus_current_path = 'org/open_power/Logging/PEL'
8 input: ['../../../../../yaml/org/open_power/Logging/PEL.interface.yaml'],
27 'org/open_power/Logging/PEL',
41 'org/open_power/Logging/PEL/Entry__markdown'.underscorify(),
43 '../../../../../yaml/org/open_power/Logging/PEL/Entry.interface.yaml',
57 'org/open_power/Logging/PEL/Entry',
/openbmc/phosphor-dbus-interfaces/gen/org/open_power/Logging/
H A Dmeson.build2 subdir('PEL') subdir
8 input: ['../../../../yaml/org/open_power/Logging/PEL.interface.yaml'],
9 output: ['PEL.md'],
21 'org/open_power/Logging/PEL',
/openbmc/phosphor-logging/extensions/openpower-pels/registry/
H A DREADME.md4 phosphor-logging using a message registry that provides the PEL related fields.
15 A component ID is a 2 byte value of the form 0xYY00 used in a PEL to:
19 2. Reside in the section header of the Private Header PEL section to specify the
33 [here](O_component_ids.json). That file can used by PEL parsers to display a
48 OpenBMC event log that the PEL is being created from.
56 This field is part of the PEL User Header section, and is used to specify the
58 PEL value. If the subsystem isn't known ahead of time, it can be passed in at
59 the time of PEL creation using the 'PEL_SUBSYSTEM' AdditionalData field. In this
79 This field is part of the PEL User Header section, and is used to specify the
80 PEL severity. It is an optional field, if it isn't specified, then the severity
[all …]
/openbmc/phosphor-dbus-interfaces/gen/org/open_power/Logging/PEL/Entry/
H A Dmeson.build3 sdbusplus_current_path = 'org/open_power/Logging/PEL/Entry'
6 'org/open_power/Logging/PEL/Entry__cpp'.underscorify(),
8 '../../../../../../yaml/org/open_power/Logging/PEL/Entry.interface.yaml',
28 'org/open_power/Logging/PEL/Entry',
/openbmc/docs/designs/
H A Derror-log-handling-for-phal.md13 (PEL) format.
19 be converted to PEL format for logging the error entry. PEL helps to improve the
40 PEL.
70 PEL: [Platform Entity Log][1]
85 data in key, value pairs so that the same can be used in the creation of PEL.
91 status need to be returned to the caller so that caller can create PEL on
97 be captured as part of the PEL.
111 interface for the creation of PEL.
119 Debug traces returned through the callback method will be added to the PEL.
126 Debug traces returned through the callback method will be added to the PEL.
[all …]
/openbmc/openbmc-test-automation/docs/
H A Dopenbmc_test_tools.md194 peltool is an open-source platform event log(PEL) tool generally used to view
200 OpenBMC PEL Tool
205 --file TEXT Display a PEL using its Raw PEL file
206 -i,--id TEXT Display a PEL based on its ID
207 --bmc-id TEXT Display a PEL based on its BMC Event ID
215 -d,--delete TEXT Delete a PEL based on its ID
218 -x Display PEL(s) in hexdump instead of JSON
/openbmc/openpower-hw-diags/attn/
H A DAttention_Handler.md61 - Platform Event Log (PEL) entry creation and debug tracing: phosphor-logging
116 submit a PEL entry on behalf of hostboot, request a hostboot dump and upon
119 PEL entry as hidden.
124 interface. For a TI with EID the attention handler will forgo creating a PEL
130 When servicing a PHYPTI the attention handler will generate a PEL entry and then
177 create at least one PEL entry containing attention handler specific FFDC. In
188 will generate a PEL entry to indicate the error that was encountered.
/openbmc/pldm/oem/ibm/libpldmresponder/
H A Dfile_io_type_pel.cpp264 PEL::RejectionReason reason{}; in fileAck()
267 reason = PEL::RejectionReason::HostFull; in fileAck()
271 reason = PEL::RejectionReason::BadPEL; in fileAck()
/openbmc/openbmc-test-automation/redfish/systems/eventlog/
H A Dtest_event_logging.robot66 Create Test PEL Log
117 Create Test PEL Log
118 Create Test PEL Log
128 Create Test PEL Log
198 Create Test PEL Log
288 Create Test PEL Log
289 Create Test PEL Log

12