Lines Matching refs:error
12 Recovery interrupts. The |EHF| document mentions various :ref:`error handling
34 error record registers from lower ELs.
49 Registering RAS error records
54 nodes contain one or more error records, which are registers through which the
55 nodes advertise various properties of the signalled error. Arm recommends that
56 error records are implemented in the Standard Error Record format. The RAS
57 architecture allows for error records to be accessible via system or
60 The platform should enumerate the error records providing for each of them:
62 - A handler to probe error records for errors;
63 - When the probing identifies an error, a handler to handle it;
64 - For memory-mapped error record, its base address and size in KB; for a system
70 notification mechanisms, the RAS framework can iterate through and probe error
71 records for error, and invoke the appropriate handler to handle it.
73 The RAS framework provides the macros to populate error record information. The
76 which are later passed to probe and error handlers.
78 For memory-mapped error records:
97 The probe handler must return a non-zero value if an error was detected, or 0
99 information resulting from probe to the error handler (see `below`__). For
104 The error handler must have the following prototype:
111 The ``data`` constant parameter describes the various properties of the error,
112 including the reason for the error, exception syndrome, and also ``flags``,
135 When the platform enumerates error records, for those records in the Standard
139 - Return non-zero value when an error is detected in a Standard Error Record;
140 - Set ``probe_data`` to the index of the error record upon detecting an error.
154 - The associated error record information (pointer to the corresponding
170 A Double Fault condition arises when an error is signalled to the PE while
171 handling of a previously signalled error is still underway. When a Double Fault
208 to through platform-supplied error records, probe them, and when an error is
209 identified, look up and invoke the corresponding error handler.
218 sorted array of interrupts to look up the error record information associated
219 with the interrupt number. That error handler for that record is then invoked to
220 handle the error.