Re:Intel acquires Linutronix
by yjftsjthsd-h on Wednesday February 23, 2022 @07:54PM
(#30448950)
I don't think anybody object to binning CPUs based on what the chip can actually do. It's when Intel decides to sell chips with features fused off even though the silicon is fully functional that people start to get annoyed.
Re:Intel acquires Linutronix
by BizarroLand on Thursday February 24, 2022 @07:54PM
(#30462466)
Also selling chips at a set MSRP and then offering to unlock the "full" potential of the chip for a low monthly fee.
It would be like buying a car and having to pay $20/month to have the 65mph speed limiter turned off.
I am impressed that this reuse is possible cheaply. I have had no exposure to the business end of this process. Indeed, my comment may be less relevant than I thought.
If it might not be clear even to the manufacturer which chip pays for which other chip, then I might give them a pass.
I suppose the only way to tell for sure would be de-lidding and comparing. But that's an expensive hobby.
I do wonder what percentage of this classification process is driven by process yield and how much is driven by volume quota requirements. I wouldn't be surprised to learn that this is an area of careful optimization; for all I know the entire silicon portfolio just ships the process yield org chart.
But all this means the user-facing FLAGS in the chip under the keyboard I'm typing this comment on is the result of a fuse configuration (aka policy), rather than a 1:1 representation of the potential of the photomask, and there are very likely a few micrometers worth of functionality I'll never get to use.
Of course I'm very curious if this is because the disabled areas were faulty (optimal use of manufacturing potential) or because *shrug* The Manufacturing Computer needed to meet its quota of Core i5s that day (arguably optimal fulfillment of volume potential). (Then there's the argument of disabling feature X across all cores for consistency, hmph.) But this is all firmly out in the weeds of implementation minutiae, and way beyond reasonable optimization; I have no idea what's theoretically broken in my CPU - and whether re-enabling that functionality explicitly to torture-test stuff I might like to make resilient would present me a relevant surface area of functionality I even knew what to do with (haven't yet played with C intrinsics for example).
At the end of the day, disabling functionality on-chip seems to be one of the few viable ways to claw fabrication yield back to something commercially viable and not utterly eye-watering, and IIUC it's been a staple for a long time.
Rereading your comment I realize it's quite possible you were writing with some or all of the above context implied and I may have misread. Not sure, disregard if so.