Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Anyone know how to figure out your CPUID? I've managed to extract the microcode .bin files from the Intel download for my processor but it contains .bin files for lots of CPU's. A lot of the microcode files when extracted are old too so I don't know why they repackage them and date the archive as though its a new release for all the listed CPUs...
This is the Intel release I'm referring to.
https://downloadcenter.intel.com/download/27431/?product=65520
Have you found evidence of the degradation due to Spectre mitigation as opposed to Meltdown or is that just a guess.
Just my two penneth,
if at present large Intel customers are held in place by 'sweetner deals - replacement contracts etc. then surely this latest security debacle would render those contracts void (equipment not fit for purpose).
On all Intel CPUs the mmu separation reduces performance by around 3.7% for general computinng.
On Haswell, kernel-only IBPB mode (MSR 0x48=1) we lose 12%, and IBPB all the time we lose 53%.
On Skylake, kernel-only IBPB mode (MSR 0x48=1) we lose 5%, and IBPB all the time we lose around 24%.
Combine the two together and it's pretty nasty. Best-case Skylake we lose 8.7% in performance with both mitigations active, kernel-only for IBPB, and we lose 27.7% performance (approximately) with bot mitigations active, IBPB on all the time. Note that none of this stuff represents a complete fix for Spectre. Not even full-on IBPB mode. It will take new hardware to get a more complete fix plus our performance back. Basically the branch prediction cache will need to tag the protection domain and either PCID or be cleared on %cr3 reload. And possibly also tag more address bits which it doesn't right now.
Maybe, but Intel's lawyers might be even sharper than their engineers.
To follow up on the ArsTechnica article and Spectre performance impacts, this is an interesting comment from a missive from one of the DragonflyBSD kernel devs:
DragonflyBSD is harder hit than either Windows or Linux, but the performance hit is real and needs to be addressed. From the end-users' perspective, many will be fortunate in that in their use cases much of the performance loss is either masked by other bottlenecks or in areas where it won't be noticed.
Fair enough for Meltdown, but for Spectre the software mitigations are proving to cause quite a performance loss in some benchmarks. I expect there's research into ways of keeping the performance benefit of speculative execution without leaking data to side channels, but I would expect any notable changes to silicon to take years to get to market.
Good articles . . . . but I still cannot find anything that breaks down the performance degradation of Meltdown vs Spectre. At this point, making an assumption that mitigating Spectre (alone) will have bigger performance issues than mitigating Meltdown + Spectre is wrong.
blanket fud without evidence seems like Intel PR
Not seen any data for AMD on that tbh, the microcode updates etc are optional. They seem fairly adamant that the chances are just about negligible of actually being effected.
@Cromulent i got my 5820k here at OCUK, not sure they would do anything about this though. Saying that, they did for the whole Nvidia 970 issue.