docs/components/ras.rst

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
102 This planned enhancement will improve robustness and correctness of asynchronous error handling
110 - **RAS_TRAP_NS_ERR_REC_ACCESS**: Trap Non-secure access of RAS error record registers.
147     Inject an unrecoverable RAS error, which gets handled in EL3.
187 Registering RAS error records
192 nodes contain one or more error records, which are registers through which the
193 nodes advertise various properties of the signalled error. Arm recommends that
194 error records are implemented in the Standard Error Record format. The RAS
195 architecture allows for error records to be accessible via system or
198 The platform should enumerate the error records providing for each of them:
200 -  A handler to probe error records for errors;
201 -  When the probing identifies an error, a handler to handle it;
202 -  For memory-mapped error record, its base address and size in KB; for a system
208 notification mechanisms, the RAS framework can iterate through and probe error
209 records for error, and invoke the appropriate handler to handle it.
211 The RAS framework provides the macros to populate error record information. The
214 which are later passed to probe and error handlers.
216 For memory-mapped error records:
235 The probe handler must return a non-zero value if an error was detected, or 0
237 information resulting from probe to the error handler (see `below`__). For
242 The error handler must have the following prototype:
249 The ``data`` constant parameter describes the various properties of the error,
250 including the reason for the error, exception syndrome, and also ``flags``,
273 When the platform enumerates error records, for those records in the Standard
277 -  Return non-zero value when an error is detected in a Standard Error Record;
278 -  Set ``probe_data`` to the index of the error record upon detecting an error.
292 -  The associated error record information (pointer to the corresponding
308 A Double Fault condition arises when an error is signalled to the PE while
309 handling of a previously signalled error is still underway. When a Double Fault
337 to through platform-supplied error records, probe them, and when an error is
338 identified, look up and invoke the corresponding error handler.
347 sorted array of interrupts to look up the error record information associated
348 with the interrupt number. That error handler for that record is then invoked to
349 handle the error.
375 .. |Image 1| image:: ../resources/diagrams/bl31-exception-entry-error-synchronization.png