4 ms·
I thought he was angry about the mitigation being disabled by default, not being unstable.
by cm2187 9y ago
I thought he was angry about the mitigation being disabled by default, not being unstable.
- icebraining 9y agoNah, it was more than that: The patches do things like add the garbage MSR writes to the kernel entry/exit points. That's insane. That says "we're trying to protect the kernel". We already have retpoline there, with less overhead.
- rocqua 9y agoThat was about patches to the linux kernel, not the microcode patches.
- icebraining 9y agoYes, but as far as I know Linus has made no comment on the microcode patches, so mm-vorticesoft is probably referring to the Spectre patches in general.
- jononor 9y agoThe microcode patches are binary blobs against a proprietary and secret ISA, how can anyone comment on their quality?
- mjevans 9y agoWhen I read it I believed that Linus was implying that the suggested mitigation was so insane that it seemed like Intel MIGHT be hiding how broken they believed their hardware was with such over-the-top reactions. As well as indirectly asking if they believed the currently accepted mitigation method (retpoline) was considered ineffective.
- sundarurfriend 9y agoHis overall point was a bewilderment at the incompetent and non-sensical patches that were being given as "fixes" in this issue. Linus was pointing out a particular instance of that, but this news and other behaviour from Intel seems to indicate this is part of an endemic, cultural, administrative issue inside the company.