3 ms·
I do agree that there are passages in this press release that are totally justified e.g. their calling attention to the fact that other processor vendors have p
by davesque 9y ago
I do agree that there are passages in this press release that are totally justified e.g. their calling attention to the fact that other processor vendors have probably been incorporating this flaw into their designs for a while. However, their seemingly innocent mentioning of AMD as being a vendor with which they are coordinating to resolve this issue appears to unfairly (and probably deliberately) implicate AMD in all of this. I feel this was an attempt to divert attention to their competitor even though their competitor's products don't suffer from this problem. I'm guessing their marketing department gave this a once over.
- 2trill2spill 9y ago> their calling attention to the fact that many other processor vendors have been incorporating this flaw into their designs for while. You have a source for this claim? Because besides for Intel's press release I can't find any evidence that other manurfacture's processors are vulnerable to this bug.
- cjbprime 9y agoThe mitigation (KAISER) is being enabled for ARM as well as Intel x86 in the Linux kernel.
- 2trill2spill 9y ago> The mitigation (KAISER) is being enabled for ARM as well as Intel x86 in the Linux kernel. Is there a commit you can point to? Or a LKML discussion about this?
- davesque 9y agohttps://lwn.net/Articles/740393/ https://lwn.net/Articles/740393/ ...which was linked-to from this article: https://arstechnica.com/gadgets/2018/01/whats-behind-the-intel-design-flaw-forcing-numerous-patches/ https://arstechnica.com/gadgets/2018/01/whats-behind-the-int...