Slashdot Mirror
Intel Says Chip-Security Fixes Leave PCs No More Than 10% Slower (axios.com)
Intel trying to defuse concern that fixes to widespread chip security vulnerabilities will slow computers, released test results late Wednesday showing that personal computers won't be affected much and promised more information on servers. From a report: The chipmaker published a table of data showing that older processors handled typical tasks 10 percent slower at most, after being updated with security patches. The information covered three generations of processors, going back to 2015, running Microsoft's Windows 10 and Windows 7 computer operating systems. Further reporting: Intel, Microsoft offer differing views on impact of chip flaw
Intel was knowingly breaking security to make their crap seem faster.
my US state's sales tax was 5% and it went up to 6% a few years ago. Everyone was pissed by a 1% change
That's a 20% change.
These people lied about every aspect of each of these major vulnerabilities. 10% is whatever, that's bad but worse is that NOBODY CAN TRUST INTEL WHATSOEVER, and they are the market leader.
Their obfuscation of the meltdown issue is unreasonably bad management, and their CEO sold a ton of shares right as the company secretly found out a year ago? The combination is absolutely toxic.
Clean house or watch it burn.
According to their chart, he oldest CPU they tested is 2.5 years old. Giving that some more proactive businesses have a 3+ year retention rate on hardware, "older" is hardly the word i'd use.
I.e. the 6700K.
I.e. all the chips have PCID
It's a bit hazy when PCID and INVPCID became supported.
This says PCID was first supported in Westmere
https://www.realworldtech.com/...
Another long overdue improvement to the page tables is the Processor Context ID (PCID). The PCID is a field in each TLB entry that associates a given page to a process. Previously, Intel's TLB could only contain entries from a single process and whenever the CR3 register was written (e.g. a context switch), the TLB was flushed. The PCID lets pages from different processes safely inhabit the TLB together, so that CR3 writes no longer flush the TLB. Whenever a process tries to access a page in memory, the PCID is checked to determine whether the page is actually mapped into the process' address space; if the PCID does not match then a TLB miss occurred. This is very much analogous to Intel's VPID, which enables the TLB to contain pages from different virtual machines and avoid TLB flushes during VM transitions.
The LWN patch says
http://lkml.iu.edu/hypermail/l...
PCIDs are generally available on Sandybridge and newer CPUs. However,
the accompanying INVPCID instruction did not become available until
Haswell (the ones with "v4", or called fourth-generation Core). This
instruction allows non-current-PCID TLB entries to be flushed without
switching CR3 and global pages to be flushed without a double
MOV-to-CR4.
I.e. it'd be interesting to see what happens on a CPU old enough not to support enough of PCID/INVPCID to optimized KPTI.
The claims of >10% hits are all for these old CPUs.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
If Intel is admitting a 10% slowdown then it must be much much larger. Because Intel and benchmarks don't live in reality.
I don't claim to be any kind of semiconductor engineer, but I am a customer that paid for something, and post-facto have a choice between insecure, or less performance than I paid for.
If you think this is fine, then you are either a paid shill or a deluded fanboy.
Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
Well, I'm no shill (and am no longer on Intel's payroll) but am a fanboi.
That said, the position you and Intel are in is commonly referred to by its acronym:
F.U.B.A.R.
There is no realistic recourse for Intel to offer that would satisfy the majority of the install base.
Full replacement at cost is likely to leave a lot of people very angry, and devastate Intel's Fiscal Year, but it is likely the best possible outcome.
Trying to make Intel replace everything affected for free (like with the FDIV bug) is a non starter. Intel can't likely even fab the old chips any more, and even if they could it would still require a redesign, so it's a non-starter. Giving everyone new chips would not be like for like, so you have issues where old software won't run, but is still required, also a non-starter. Additionally, both those options would likely bankrupt the company entirely, meaning people *still* wouldn't get replacements, and you'd have 100K freshly unemployed.
The most likely outcome I see is a rebate/coupon towards the purchase of any system containing a new Intel CPU from any vendor where the dollar value of the rebate is tied to the age/sku of the old CPU, with no or soft requirements to return the old CPU.
What would you (as a consumer) expect?
I likely won't get squat, since all my CPUs are samples that employees were given at various times, or bought via employee purchase channels.
whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
Exaggeration isn't necessary. Even taking Intel at their word, that 10% differential has been their selling point for years. That means the very reason people bought Intel over the competitor is now bunk. At the very least, consumers are due a rebate, and that only (barely) addresses the lost value to those consumers, to say nothing about the damage Intel caused to its competitors in peddling this lie.
The 10% figure sure sounds negligible... until you give it more than five seconds of critical thought. Any way you slice it, Intel reaped illegitimate profits. And instead of making it right, they're busy trying to discredit the very people who have supported them over the years: their customers. This is the gold standard of how not to handle a situation like this.