Home
last modified time | relevance | path

Searched refs:CPER (Results 1 – 13 of 13) sorted by relevance

/openbmc/libcper/
H A DREADME.md1 # CPER JSON Representation & Conversion Library
3 This repository specifies a structure for representing UEFI CPER records (as
6 standard CPER binary format and the specified structured JSON.
24 This project comes with several binaries to help you deal with CPER binary and
25 CPER-JSON. The first of these is `cper-convert`, which is a command line tool
26 that can be found in `build/`. With this, you can convert to and from CPER and
27 CPER-JSON through the command line. An example usage scenario is below:
35 This allows you to generate pseudo-random valid CPER records with sections of
45 Finally, a static library containing symbols for converting CPER and CPER-JSON
56 The specification for this project's CPER-JSON format can be found in
[all …]
H A Dmeson.build134 description: 'C bindings for parsing CPER',
/openbmc/docs/designs/
H A Dcper-records.md1 # CPER records - CPER
9 Server CPUs expose a managability interface refered to as CPER records. A user
15 CPER stands for Common Platform Error Record and is defined as an industry
21 In Redfish specification drop 2021.3, Redfish added support for CPER records
23 decoded CPER instance. In addition to Redfish, there is a proposed DMTF
24 interface for sending CPER log events to the BMC using [MCTP/PLDM][cperevent],
27 ARM has developed a reference library for decoding CPER records that does not
38 - A BMC should be able to decode binary CPER records originated from a CPER
41 - BMC should be able to recieve and decode CPER records from a CPU per the [CPER
50 promised in the CPER specification.
[all …]
/openbmc/libcper/docs/
H A DOEMExtensions.md11 section from CPER -> CPER-JSON and CPER-JSON -> CPER. For the purposes of
12 example here, we will create a fake CPER section, "myVendorSection", in
53 //Define a method here that converts the given JSON IR object into CPER binary,
96 * Describes available sections to the CPER parser.
105 //Definitions of all sections available to the CPER parser.
113 other conversion libraries included should successfully convert your OEM CPER
114 section between CPER-JSON and CPER binary.
H A DGeneratorExtensions.md78 * Describes available section generators to the CPER generator.
/openbmc/qemu/docs/specs/
H A Dacpi_hest_ghes.rst1 APEI tables generating and CPER record
36 | | read_ack_write | | | | | CPER | | | |
37 + +--------------------------| | | | | CPER | | | |
39 + +--------------------------+ | | | | CPER | | | |
43 | | error_status_address-----+-------+ | | | CPER | | |
44 | | ................. | | | | CPER | | |
52 | | CPER | |
53 | | CPER | |
55 | | CPER | |
97 (9) When QEMU gets a SIGBUS from the kernel, QEMU writes CPER into corresponding
[all …]
H A Dacpi_erst.rst119 shows two records (in CPER format) in the backend storage, while the
131 2 | CPER |
133 3 | CPER |
141 of CPER record_id's to efficiently access records in the backend
177 CPER record in the corresponding slot. Stated differently, the
178 location of a CPER record_id in the record_id[] array provides the
183 CPER record_id. Instead slot 1 is the first available slot and thus
184 record_id_[1] may contain a CPER.
/openbmc/libcper/generator/
H A DREADME.md3 This project allows you to generate pseudo-random CPER records for software
4 testing purposes. The records are compliant (to an extent) with the CPER
15 This command would generate a CPER log with a processor generic section, VT-d
26 that translating from CPER binary -> JSON -> CPER binary yields the same
/openbmc/bmcweb/redfish-core/include/generated/enums/
H A Devent.hpp25 CPER, enumerator
46 {DiagnosticDataTypes::CPER, "CPER"},
H A Dlog_entry.hpp29 CPER, enumerator
70 {LogDiagnosticDataTypes::CPER, "CPER"},
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/
H A DFaultLogType.interface.yaml9 - name: CPER
/openbmc/libcper/specification/document/
H A Dcper-json-specification.tex7 \title{CPER-JSON Specification}
120 This structure describes the error severity of a single CPER record.
142 This structure describes the notification type of a single CPER record.
152 This structure describes the enabled flag on a given CPER record header.
191 This structure describes the enabled flags on a given CPER section descriptor.
210 % Generic CPER structures.
211 \section{Generic CPER Structures}
217 This structure describes the revision of a single CPER record or sub-structure.
222 \jsontableend{CPER revision structure field table.}
227 This structure describes the a generic CPER error status, that can be used by any CPER section.
[all …]
/openbmc/linux/Documentation/admin-guide/
H A Dras.rst335 Platform Error Record (CPER) section to be an SMBIOS Memory Device