> (a) is a trap, not an exception - so the instruction has been done, > and you don't need to try to emulate it or anything to continue. Maybe for errors on the data side of the pipeline. On the instruction side we can usually recover from user space instruction fetches by just throwing away the page with the corrupted instructions and reading from disk into a new page. Then just point the page table to the new page, and hey presto, its all transparently fixed (modulo time lost fixing things). -Tony
