If anything, it bothers me more! Why would they get special treatment, and why would I have to subsidize its features paying for my CPU to have it, but disabled?
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.
It would be like buying a car and having to pay $20/month to have the 65mph speed limiter turned off.
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 would also argue you aren’t subsidizing the feature, they are subsidizing your budget chip.
That's how it starts. First it happens to people whose needs you can't relate to, and then one day they'll want extra money so the accelerated video support starts working again.
It should bother you.
That was bothering me a bit too, but then I realized it may have a use that most of us don't care about. Sure they could charge more for AVX512 or whatever, and they might try to charge rent for such options which I'm not a fan of. But what if they are being asked by 3-letter agencies for chips with custom circuitry that would be relatively low volume, somewhat annoying to produce? If it's not too much area they could just add those features to every CPU and only enable them for those agencies via SDSi interface. Just speculation in a direction that is IMHO less awful than excess monetization.