Re:Intel SA-00145: Lazy FP State Restore
by ajross on Wednesday June 13, 2018 @10:30PM
(#17308796)
All CPUs speculate to some extent (branch prediction has been on everything for basically 30 years now). Intel CPUs got hit first because they're the first ones to speculate so deeply that you can discriminate cache behavior like this. The caches and pipelines just aren't big enough elsewhere, but the techniques are all the same.
[ Parent
| on HN ]
Nope, Intel got hit because they did it wrong, and the others did it right. If you speculate you need two status registers. One for the good and one for the bad case.
Same for meltdown: you need one for the kernel and one for user space. Intel didn't care, others do.
But Intel got the government ("legal") backdoors in. Priorities.
What are you talking about?
Re:Intel SA-00145: Lazy FP State Restore
by Tuna-Fish on Thursday June 14, 2018 @01:45PM
(#17313622)
Meltdown was caused by Intel not checking privileges correctly in a speculated context, choosing to defer such checks as long as possible. This allowed the worst and easiest to use exploit, making it possible to read from any mapped location in memory. Most other CPUs did things right even in speculated contexts.
(Intel wasn't quite alone in this, though -- at least one ARM core also had this issue.)