News for hackers. Stuff that matters.

A comment on Google Cloud Platform is the first cloud provider to offer Intel Skylake. Parent comment

Re:Google Cloud Platform is the first cloud provider to offe... by Cyph0n on Friday February 24, 2017 @11:31AM (#13725083)
Intel's FDIV bug was an outlier. Besides, nowadays most of the ISA is implemented in microcode[1]. There are two advantages to this approach: 1) it is much easier to verify the microcode unit (it's simpler/smaller), and 2) it allows CPU vendors to "fix" ISA implementation issues post-release by issuing microcode updates.

[1]: ISA => microcode is equivalent in some respects to C => LLVM IR

[ Parent | on HN ]
Re:Google Cloud Platform is the first cloud provider to offe... by mtanski on Friday February 24, 2017 @12:03PM (#13725429)
Outlier? I would say uncommon but not an outlier. Here's a non-exhaustive list. http://wiki.osdev.org/CPU_Bugs

There was also an issue with transaction memory with both Haswel & Broadwell. The fix was to disable TSX support via micro code update. I wouldn't call disabling a fix personally. I doubt Intel even compensated the folks who bought it for the TSX support.

[ Parent | on HN ]
Re:Google Cloud Platform is the first cloud provider to offe... by puzzle on Friday February 24, 2017 @02:03PM (#13726586)
Yeah, that list is far from exhaustive. Years and years ago, Google's websearch cluster validation suite found a tricky bug that isn't on that list. The exchange with the CPU manufacturer was amusing.
[ Parent | on HN ]
Re:Google Cloud Platform is the first cloud provider to offe... by Cyph0n on Friday February 24, 2017 @12:21PM (#13725594)
Given how many Intel/AMD/etc. CPU releases there have been, I would still refer to such glaring implementation bugs as outliers.
[ Parent | on HN ]
Re:Google Cloud Platform is the first cloud provider to offe... by bonzini on Friday February 24, 2017 @01:32PM (#13726267)
Most of the ISA may be implemented in microcode, but the parts that matter are certainly not microcoded!

For example the TLB access and the fast path of the TLB miss are not microcoded. You only get to microcode if you have to set an accessed bit or a dirty bit, or if there is a page fault.

[ Parent | on HN ]