If you talk about "how stupid Intel's engineers were a decade ago" re:CPU flaws on social media without an engineering background, I think you should be banned from Twitter until you read the Intel assembly manuals cover to cover. Either that or some similarly ironic punishment.
-
-
Does that mean we can have security-tagged CPU & memory architectures now?
-
Not a solution. Every untaken branch is fundamentally a privilege boundary. You can't scale to that many tags.
-
Speculation must either not happen, or happen in containment outside of which no speculative results can be seen.
-
hence xfence instructions are finally put to use ?
-
No, because that's imposing a new ISA constraint not satisfied by existing binaries, it's opt-in, and it pessimizes non-broken cpu implementations. The cpu needs to do the right thing itself, not only when assisted by a pessimizing compiler.
-
Nothing to argue with that. This confirms my understanding fixes are not made to last as effective mitigations on current processors would require massive patching across bios, kernel, apps, libs. (right?)

-
I am convinced any cloud vm with root access is a gonner regardless of patching.
-
I think vm's are actually easier to make safe if the host isn't cost-cutting. Just doing full flush of entire cache hierarchy at every vm switch covers most of it.
- 2 more replies
New conversation -
-
-
My uncle was an INTEL CPU engineer DOU anyone? LOL he retired 2yrs ago, sadly no spectre info. I know computers rather well consider myself too have a sufficient intelligence. However when he talks pipelines or FORTRAN I am lost it is another world all together hardware...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.