It's a compromise, I would prefer a more specific check. Not sure what alternative you're proposing, just start depending on how obscure parts of the spec works under attack without even testing?
Maybe you get "lucky" with some chip and there's some extreme manufacturing variation that causes this failure mode, maybe the wafer was bad in some particular way, etc.
-
-
testing a set of chips from one uarch form one vendor and having it pass some particular overclocked test (where passing means not corrupting the EIP while not crashing?) tells you as much about another uarch from the same vendor as it does about a chip from another vendor.
-
It doesn't even tell you much about another stepping from the same chip (and vendors will sometimes release revisions without updating the stepping since OEMs complain when you officially change the stepping).
- 22 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.
