3 ms·
Fair point, but again most Windows programs aren't designed with heterogeneous CPUs in mind, so probably they don't want to deal with the headaches, plus the sp
by zinekeller 5y ago
Fair point, but again most Windows programs aren't designed with heterogeneous CPUs in mind, so probably they don't want to deal with the headaches, plus the space used for AVX-512 (note that it's now in microcode) can be repurposed for more important tasks.
Of course, this could be evil Intel playing its tricks again but financially speaking removing AVX-512 do have tangible benefits to them in the form of increased microcode for the rest of the instructions (I want to see the detailed Alder Lake errata, maybe there's indeed a bug in another instruction that requires more microcode to implement - AVX-512 is an easy sacrifice for that).
- marcan_42 5y agoIt's not in microcode, they're just disabling it in a microcode update. Microcode updates aren't replacements for microcode either, they're patches. The vast majority of microcode is in ROM and can never be changed wholesale; updates can just patch in hooks and change certain things, limited by the number of patch slots available. Doing this does not "free up" any microcode. It's purely disabling a feature, there is absolutely nothing to be gained in return.