Nick Maclaren wrote: > Er, no. Try a machine-check in a TLB miss handler. But it is all > pretty irrelevant, as the problem arises with asychronous exceptions > (e.g. timer interrupts, signals from other processes), anyway. But we weren't talking about asynchronous exceptions, we were talking about floating point exceptions. Unless your TLB miss handler uses floating point arithmethic, there's no way it can get interrupted by one. (And if it does use floating point arithmetic in a way that can cause an exception, you'd better write it to deal with that!) -- Greg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4