blob: ad2a9a3c69340dbc26a58419507ba5dcba02c5f6 [file] [log] [blame]
Vijay Lobo8c71ba72021-06-24 23:37:30 -05001description: >
2 Implement to provide PEL event/error entry attributes.
3properties:
4 - name: Hidden
5 type: boolean
6 default: false
7 description: >
Patrick Williams8da396c2022-03-14 14:21:02 -05008 Hidden Error - This flag allows events to be placed in a system, but
9 remain hidden from the customer. This event log is visible to
10 development personnel only, e.g. hardware recovered error, etc. No
11 service action is required for this type of errors. In general, when
Patrick Williamsa1347412022-12-06 10:56:22 -060012 this value is used, the Error Action Flags has the value of "Hidden
13 Error". An event log with this value is used primarily for error
14 thresholding design/code debug or as a record to indicate an error
15 frequency or trend.
Vijay Lobo8c71ba72021-06-24 23:37:30 -050016 - name: Subsystem
17 type: string
18 description: >
Patrick Williams8da396c2022-03-14 14:21:02 -050019 A free form, implementation defined string which uniquely and
20 permanently identifies a specific subsystem string. This field should
21 not be used for programmatic interrogation of an object.
Vijay Lobo3e9aa3b2021-08-11 17:24:53 -050022 - name: ManagementSystemAck
23 type: boolean
24 default: false
25 description: >
Patrick Williamsa1347412022-12-06 10:56:22 -060026 Notifies the PEL handler that the management system acknowledged a
27 PEL. The management system can be any system monitoring the hardware.