Anyone want to place bets on whether the first actual fix for Spectre will be via reverse engineered and patched microcode?https://twitter.com/thorstenholz/status/1031839729145311232 …
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
This has no relevance to the topic at hand because the attack code doesn't have any relation to the host ISA and no need to know anything about the host running the emulator.
We can also solve L1TF with shadow paging. This was the original rationale for the work on the rv8 JIT engine. Use RISC-V as the IR for dynamic runtime translation/obfuscation with multiple entropy vectors. RISC via CISC to a microop backend. It is however a bit of a pipe dream.
Do you mean Foreshadow? AIUI it's solvable just by not putting data in the unused private bits of not-present PTEs.
But given how awful Intel's been I'd be tempted just to not use PTEs at all, TLBs only, faulting on every miss.
Disclosure vs Remote Execution. The Usenet microcode paper covers multiple potential microcode based mitigations.
It does in the context of the r cent Usenet paper on microcode mitigation’s it is one of the described applications of microcode based mitigations. It doesn’t help speculation but blinding would i.e. random evictions. I’m thinking from a wider context than just Spectre attacks.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.