AMD Security Statement from CTO and SVP Mark Papermaster
Click here to post a comment for AMD Security Statement from CTO and SVP Mark Papermaster on our message forum
Embra
Thanks HH.
schmidtbag
So basically just Variant 2 is noteworthy (but not necessarily crucial).
At least a high-up representative from AMD finally gave a solid answer. I was getting a bit tired of all the pussyfooting AMD was doing for the past couple weeks.
nevcairiel
Didn't AMD basically start with "We're not affected" when the news first broke? Long way to go from "not" to two variants actually being applicable. Sure, Meltdown is Intel only, but Spectre might be as bad or possibly even worse in the long run.
D3M1G0D
schmidtbag
nevcairiel
D3M1G0D
fantaskarsef
Those security flaws wouldn't be scary at all if they were patched right away properly, not half heartedly and technically lacking like with AMD systems and their non-bootability issues, not producing random reboots in Haswell systems, and that's just what we know so far. We've yet to see any real exploit, and so far (if you don't consider the possible damage) all we've got from this is a slow down of systems and more borken patches / updates.
schmidtbag
fantaskarsef
https://www.blog.google/topics/google-cloud/protecting-our-google-cloud-customers-new-vulnerabilities-without-impacting-performance/
Well, I am fairly aware that the issues here come from the way that Intel's chips "predict" usage in the first place, so thanks for your consideration. I've read the links posted here by others (you iirc too).
Then again, deactivating those speculative executions does not make a system not boot or reboot unprovoced by the user.
By the way, google has found a software resolution with marginal performance impact on their server systems while still keeping their systems secure.
schmidtbag