Live data from Hacker News

Intel Issues New CPU Microcode for New, Undisclosed Security Updates

phoronix.com

11–15 of 15 posts

Re: Intel Issues New CPU Microcode for New, Undisclosed Security Updates

#11
A nice test would be to compare a "cpuid -1 -r" before and after applied microcode updates. To check if new bit(s) is set somewhere.

Worth might be to check if IA32_ARCH_CAPABILITIES contain new bits set as well on some platforms which would indicate they are not affected. Via the NO_xxx flag.

Re: Intel Issues New CPU Microcode for New, Undisclosed Security Updates

#12
post #9
post #6

Phoronix certainly has strong technical background. However, I am not friend of their sometimes dramatic writing style. I call them the Linux yellow press :) Let's wait and see whether that SA comes and whether it brings something big.

Phoronix is where AMD is infallible and Intel/NVIDIA are evil incarnates. And that results in news pieces like this.

Ah, I don't read it frequently enough to have noticed such bias.

Re: Intel Issues New CPU Microcode for New, Undisclosed Security Updates

#14
post #9
post #6

Phoronix certainly has strong technical background. However, I am not friend of their sometimes dramatic writing style. I call them the Linux yellow press :) Let's wait and see whether that SA comes and whether it brings something big.

Phoronix is where AMD is infallible and Intel/NVIDIA are evil incarnates. And that results in news pieces like this.

Given the Linux bent, it makes sense considering AMD's relationship with the open source community relative to Intel's, and to an even greater extent NVIDIA's.

You already know this clip: https://www.youtube.com/watch?v=iYWzMvlj2RQ

Re: Intel Issues New CPU Microcode for New, Undisclosed Security Updates

#15
post #2

It's been long enough, can we please just have Intel (YEAR) CPU as a reference rather than the eternally opaque codenames? https://en.wikipedia.org/wiki/Coffee_Lake Intel 2017+ CPUs (Coffee Lake+).

Absolutely. And have you run across the phrase "previously called xxxlake?" [1] was all I could lay my hands on quickly. It's confusing when for ex. you're trying to figure out Intel pmu msr addresses.

https://ark.intel.com/content/www/us/en/ark/products/codenam...

Post reply on HN