Interrupt Context Support

Currently when in interrupt context their is no way to introspect the running instruction that the normal context was at when executing this vector, also their is no way to change the address to return to. This limits what you can do in interrupt context, for example using an undefined instruction to emulate floating point and needing to know what instruction and its arguments caused the error. Secondly, interrupts always vector back to the originating address, so if you wanted to use the timer interrupt to do multi-programming, we would need to be able to control the iret address so you can "jump" to a new process.

Proposed implementation: Expose the IVBT in a mem map so you can read the PC and pass that to iret Make IRET use RC+I for the vector return address

Comments (1)