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
Considering branch prediction & speculative loading is very likely on the hot path, I don’t think it’s implemented in microcode :/
But if the problem is branch predictor injection, they can just flush branch predictor state on kernel/userspace transitions. That likely wouldn't have a massive performance impact.
I may be wrong but I don’t think there is any mechanism in place to do that. And even then by the time the context switch is actually executed, you may already have speculatively executed further instructions
There is no *user-accessible* architecturally defined mechanism for that that I'm aware of, but it's entirely possible they have a way of doing it in microcode. "Flush/disable/whatever the BTB" sounds like the kind of chicken bit they'd have. Hence microcode fix.
We also have to keep in mind that flushing pipeline/caches every time a program use a syscall may have an even bigger perf impact than KPTI
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
