Lines Matching refs:error

33 -  Kernel is prohibited from accessing the RAS error records directly
35 -  Firmware signals error back to Kernel via SDEI
60 the std error records directly.
64    to lower EL. This happens when there is an error (EA) in the system which is not yet
81 - **RAS_TRAP_NS_ERR_REC_ACCESS**: Trap Non-secure access of RAS error record registers.
118     Inject an unrecoverable RAS error, which gets handled in EL3.
158 Registering RAS error records
163 nodes contain one or more error records, which are registers through which the
164 nodes advertise various properties of the signalled error. Arm recommends that
165 error records are implemented in the Standard Error Record format. The RAS
166 architecture allows for error records to be accessible via system or
169 The platform should enumerate the error records providing for each of them:
171 -  A handler to probe error records for errors;
172 -  When the probing identifies an error, a handler to handle it;
173 -  For memory-mapped error record, its base address and size in KB; for a system
179 notification mechanisms, the RAS framework can iterate through and probe error
180 records for error, and invoke the appropriate handler to handle it.
182 The RAS framework provides the macros to populate error record information. The
185 which are later passed to probe and error handlers.
187 For memory-mapped error records:
206 The probe handler must return a non-zero value if an error was detected, or 0
208 information resulting from probe to the error handler (see `below`__). For
213 The error handler must have the following prototype:
220 The ``data`` constant parameter describes the various properties of the error,
221 including the reason for the error, exception syndrome, and also ``flags``,
244 When the platform enumerates error records, for those records in the Standard
248 -  Return non-zero value when an error is detected in a Standard Error Record;
249 -  Set ``probe_data`` to the index of the error record upon detecting an error.
263 -  The associated error record information (pointer to the corresponding
279 A Double Fault condition arises when an error is signalled to the PE while
280 handling of a previously signalled error is still underway. When a Double Fault
308 to through platform-supplied error records, probe them, and when an error is
309 identified, look up and invoke the corresponding error handler.
318 sorted array of interrupts to look up the error record information associated
319 with the interrupt number. That error handler for that record is then invoked to
320 handle the error.
346 .. |Image 1| image:: ../resources/diagrams/bl31-exception-entry-error-synchronization.png