Home
last modified time | relevance | path

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

12

/openbmc/phosphor-dbus-interfaces/yaml/org/open_power/Logging/
H A DPEL.interface.yaml6 Returns a file descriptor to a PEL.
11 The PEL log ID of the PEL to retrieve.
33 The PEL data
39 Notifies the PEL handler that the host (usually the OS) acked a PEL.
44 The PEL log ID
50 Notifies the PEL handler that the host could not process a PEL.
55 The PEL log ID
115 - PEL log ID: The unique ID of the PEL
127 The BMC event log id of the PEL to retrieve the PEL id.
132 The Id of the PEL.
[all …]
/openbmc/openbmc-test-automation/openpower/pel/
H A Dtest_bmc_pel.robot32 Create Test PEL Log
37 Verify PEL Log Details
44 Create Test PEL Log
90 Create Test PEL Log
104 Create Test PEL Log
113 Verify PEL ID Numbering
118 Create Test PEL Log
123 # Example of PEL IDs from PEL logs.
677 Verify PEL Delete
840 Get PEL Log IDs
[all …]
/openbmc/phosphor-logging/extensions/openpower-pels/
H A Dpel.hpp62 class PEL class
65 PEL() = delete;
66 ~PEL() = default;
67 PEL(const PEL&) = delete;
68 PEL& operator=(const PEL&) = delete;
69 PEL(PEL&&) = delete;
70 PEL& operator=(PEL&&) = delete;
84 explicit PEL(std::vector<uint8_t>& data);
94 PEL(std::vector<uint8_t>& data, uint32_t obmcLogID);
111 PEL(const openpower::pels::message::Entry& entry, uint32_t obmcLogID,
H A Dpel.cpp55 PEL::PEL(const message::Entry& regEntry, uint32_t obmcLogID, uint64_t timestamp, in PEL() function in openpower::pels::PEL
203 PEL::PEL(std::vector<uint8_t>& data) : PEL(data, 0) {} in PEL() function in openpower::pels::PEL
205 PEL::PEL(std::vector<uint8_t>& data, uint32_t obmcLogID) in PEL() function in openpower::pels::PEL
229 bool PEL::valid() const in valid()
250 void PEL::setCommitTime() in setCommitTime()
256 void PEL::assignID() in assignID()
286 size_t PEL::size() const in size()
323 void PEL::checkRulesAndFix() in checkRulesAndFix()
518 bool PEL::isHwCalloutPresent() const in isHwCalloutPresent()
587 bool PEL::getDeconfigFlag() const in getDeconfigFlag()
[all …]
H A DREADME.md1 # OpenPower Platform Event Log (PEL) extension
15 - [PEL Retention](#pel-retention)
19 - [PEL Archiving](#pel-archiving)
35 RAWPEL=<path to PEL File>
213 PEL:
224 ## The PEL Message Registry
440 PEL.
460 out in the PEL spec.
489 ## PEL Retention
500 PEL has been added and the method to create the PEL has returned to the caller,
[all …]
H A Dmanager.hpp28 sdbusplus::org::open_power::Logging::server::PEL>;
240 std::string getResolution(const openpower::pels::PEL& pel) const;
247 std::string getEventId(const openpower::pels::PEL& pel) const;
279 void updateProgressSRC(std::unique_ptr<openpower::pels::PEL>& pel) const;
408 void checkPelAndQuiesce(std::unique_ptr<openpower::pels::PEL>& pel);
418 void updateEventId(std::unique_ptr<openpower::pels::PEL>& pel);
450 bool updateResolution(const openpower::pels::PEL& pel);
459 void updateDBusSeverity(const openpower::pels::PEL& pel);
499 openpower::pels::PEL& pel);
H A Drepository.hpp170 void add(std::unique_ptr<PEL>& pel);
228 using ForEachFunc = std::function<bool(const PEL&)>;
248 using AddCallback = std::function<void(const PEL&)>;
455 void archivePEL(const PEL& pel);
457 using PELUpdateFunc = std::function<bool(PEL&)>;
493 void processAddCallbacks(const PEL& pel) const;
516 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 Dhost_notifier.hpp172 void newLogCallback(const PEL& pel);
194 bool addPELToQueue(const PEL& pel);
H A Drepository.cpp96 PEL pel{data}; in restore()
170 void Repository::add(std::unique_ptr<PEL>& pel) in add()
205 void Repository::write(const PEL& pel, const fs::path& path) in write()
337 PEL pel{data}; in for_each()
354 void Repository::processAddCallbacks(const PEL& pel) const in processAddCallbacks()
408 PELUpdateFunc func = [state](PEL& pel) { in setPELHostTransState()
434 PELUpdateFunc func = [state](PEL& pel) { in setPELHMCTransState()
459 PEL pel{data}; in updatePEL()
778 void Repository::archivePEL(const PEL& pel) in archivePEL()
H A Dmanager.cpp141 auto pel = std::make_unique<openpower::pels::PEL>(pelData, obmcLogID); in addPEL()
375 auto pel = std::make_unique<openpower::pels::PEL>( in createPEL()
675 void Manager::checkPelAndQuiesce(std::unique_ptr<openpower::pels::PEL>& pel) in checkPelAndQuiesce()
713 std::string Manager::getEventId(const openpower::pels::PEL& pel) const in getEventId()
738 void Manager::updateEventId(std::unique_ptr<openpower::pels::PEL>& pel) in updateEventId()
760 std::string Manager::getResolution(const openpower::pels::PEL& pel) const in getResolution()
826 bool Manager::updateResolution(const openpower::pels::PEL& pel) in updateResolution()
847 void Manager::updateDBusSeverity(const openpower::pels::PEL& pel) in updateDBusSeverity()
989 std::unique_ptr<openpower::pels::PEL>& pel) const in updateProgressSRC()
1035 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()
201 auto pel = std::make_unique<PEL>(data); in TEST_F()
221 pel = std::make_unique<PEL>(data); in TEST_F()
360 PEL newPEL{*pelData}; in TEST_F()
374 PEL newPEL{*pelData}; in TEST_F()
403 PEL newPEL{*pelData}; in TEST_F()
417 PEL newPEL{*pelData}; in TEST_F()
456 PEL newPEL{newData}; in TEST_F()
513 pel = std::make_unique<PEL>(data); in TEST_F()
530 pel = std::make_unique<PEL>(data); in TEST_F()
[all …]
H A Dpel_test.cpp136 pel = std::make_unique<PEL>(data); in TEST_F()
214 PEL pel2{ in TEST_F()
297 PEL pel{data}; in TEST_F()
341 PEL pel{data}; in TEST_F()
460 PEL pel{data}; in TEST_F()
871 PEL pel{ in TEST_F()
921 PEL pel{ in TEST_F()
1160 PEL pel{ in TEST_F()
1186 PEL pel{ in TEST_F()
1217 PEL pel{ 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()
/openbmc/phosphor-dbus-interfaces/gen/org/open_power/Logging/PEL/
H A Dmeson.build4 input: [ '../../../../../yaml/org/open_power/Logging/PEL.interface.yaml', ],
12 'org/open_power/Logging/PEL',
18 'org/open_power/Logging/PEL/Entry__markdown'.underscorify(),
19 input: [ '../../../../../yaml/org/open_power/Logging/PEL/Entry.interface.yaml', ],
27 'org/open_power/Logging/PEL/Entry',
/openbmc/phosphor-dbus-interfaces/gen/org/open_power/Logging/
H A Dmeson.build2 subdir('PEL') subdir
5 input: [ '../../../../yaml/org/open_power/Logging/PEL.interface.yaml', ],
6 output: [ 'PEL.md' ],
13 '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:
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.
81 of the OpenBMC event log will be converted into a PEL severity value.
141 PEL action flags, as defined by the PEL spec. It is an array of enumerations.
185 - BB = PEL subsystem as mentioned above
228 words will be set to zero in the PEL.
329 There is room for up to 10 callouts in a PEL.
573 The PEL daemon can be told to capture pieces of the journal in PEL UserData
[all …]
/openbmc/phosphor-dbus-interfaces/gen/org/open_power/Logging/PEL/Entry/
H A Dmeson.build3 'org/open_power/Logging/PEL/Entry__cpp'.underscorify(),
4 input: [ '../../../../../../yaml/org/open_power/Logging/PEL/Entry.interface.yaml', ],
12 '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]
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.
133 Debug traces returned through the callback method will be added to the PEL.
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/org/open_power/Logging/PEL/
H A DEntry.interface.yaml2 Implement to provide PEL event/error entry attributes.
26 Notifies the PEL handler that the management system acknowledged a
27 PEL. The management system can be any system monitoring the hardware.
32 PEL. It is the unique ID for a single event. Multiple PELs can be
48 The creation timestamp of the PEL in milliseconds since the epoch. For
/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.md59 - Platform Event Log (PEL) entry creation and debug tracing: phosphor-logging
114 submit a PEL entry on behalf of hostboot, request a hostboot dump and upon
117 PEL entry as hidden.
122 interface. For a TI with EID the attention handler will forgo creating a PEL
128 When servicing a PHYPTI the attention handler will generate a PEL entry and then
175 create at least one PEL entry containing attention handler specific FFDC. In
186 will generate a PEL entry to indicate the error that was encountered.
/openbmc/openbmc/meta-openpower/recipes-phosphor/logging/
H A Dhostboot-pel-parsers_git.bb1 SUMMARY = "Hostboot PEL python parsers"

12