The architectural implications are so profound. What should a CPU even do? Re-evict all speculatively filled lines?!https://twitter.com/acmsigarch/status/948719659423096832 …
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
No, simple. Loads whose address depend on another speculative load should never be executed speculatively.
That seems incredibly costly—maybe not much better than disabling speculation altogether. Re-eviction is a lazy approach to the same goal.
Re-eviction doesn't help in the presence of HT that could view the temporary effect.
if the data is already in L1 it should be ok... at least for this attack... but performance impact will be very high: generate cache-miss early with speculation gives a big performance boost to out of order cpu
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.