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
I didn't find the time to run this test for the paper, so thank you so much for actually doing it! It was clear it'd be bad given that they put the effort in to add an MSR to disable the mitigations again. It's about the level of performance hit I expected, but.. ouch. Very ouch.
It was just a quick sysbench thing, not even sure exactly what kind of memory workload it's using, vs "a: rdrand %rax; jmp a", but yeah.... it looks pretty bad.
might be interesting to see what happens if one wouldn't loop around a single rdrand but a block of 16 or more and see if it makes it even worse.
I tried that but it didn't seem to be much worse. I think the overhead of the jump is negligible.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
