I'd be curious to know how reading CPU errata is helpful. A typical errata will say something like "under certain conditions, unexpected behavior may occur" and it will then describe corruption of {cache, registers, IP, flags, etc.} What can any software do to work around that?
I have to say, I can't say I'm particularly interested in your opinion of a paper you haven't read. I don't think you understand the security model, which perhaps you should have made an effort to do before criticizing. 
-
-
What is this paper? Where could I read it? I find these sort of HW/Sw codesign challenges very interesting!
-
This is it, it's a software fault isolation system for x86. It's no longer used, but was widely deployed for a while. https://research.google.com/pubs/archive/34913.pdf …
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.