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 looked at microcode_amd_fam17h.bin (supposed microcode fix for Spectre) and it *only* applies to fam17h model 1 stepping *2*. Which as far as I can tell is EPYC. My Threadripper is stepping *1* and is *NOT* updated by this microcode. So consumer CPUs are NOT fixed yet.
If anyone has a Stepping 2 retail CPU I'd like to hear about it, but as far as I can tell from some google-sleuthing, that's EPYC. Signature is 0x80f12 (the 12 means model 1 stepping 2), updated ucode version is 0x08001213. My TR is still on 0x08001129 and has sig 0x80f11.
Yeah, I tried hacking the equivalence table to force it to try to load, and it fails. It's not just a signature omission; that microcode does NOT apply to my CPU.
It's possible that AMD cooked up a new stepping in time for the EPYC release and they just released the microcode for it only for enterprise customers, which would be guaranteed to have stepping 2. So maybe retail chips of that stepping exist, but most would be 1, SOL for now.
Where do the Ryzen chips fit in? My new Dell tower isn't listed in any of their Spectre/Meltdown docs...
Same as Threadripper. Check your stepping in /proc/cpuinfo and/or cpu-z but I bet it's 1.
I think @michaellarabel did some benchmarks with KPTI that showed slowdown on Epyc, but not much on standard zen. Makes sense now.
KPTI is disabled outright on AMD processors since they are not vulnerable. This is about IBRS/IBPB.
Realistically though, you don't need any updated microcode to mitigate Spectre. http://developer.amd.com/wordpress/media/2013/12/Managing-Speculation-on-AMD-Processors.pdf …
Variant 1 requires code fixes. Even newer CPUs or microcode aren't going to fix that one in *all* cases. Variant 2 can be worked around with compiler patches but having the microcode fix means you can use existing binaries and may be faster in *some* microarchitectures.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
