Visible to Intel only — GUID: iga1409336736964
Ixiasoft
Visible to Intel only — GUID: iga1409336736964
Ixiasoft
3.7.10. Handling Nested Exceptions
- An exception handler enables maskable interrupts
- An EIC is present, and an NMI occurs
- An EIC is present, and the processor is configured to keep maskable interrupts enabled when taking an interrupt
- An exception handler triggers an instruction-related exception
For details about when the Nios® II processor takes exceptions, refer to “Exception Processing Flow” on page 3–44.
For details about unimplemented instructions, refer to the Processor Architecture chapter of the Nios® II Processor Reference Handbook.
For details about MMU and MPU exceptions, refer to the Instruction-Related Exceptions section of this chapter.
A system can be designed to eliminate the possibility of nested exceptions. However, if nested exceptions are possible, the exception handlers must be carefully written to prevent each handler from corrupting the context in which a pre-empted handler runs.
If an exception handler issues a trap instruction, an optional instruction, or an instruction which could generate an MMU or MPU exception, it must save and restore the contents of the estatus and ea registers.