4 ms·
If instructions don't run the same between heterogenous cores, i.e. one core supports instructions the other doesn't, unless this information is available to th
by dwattttt 3y ago
If instructions don't run the same between heterogenous cores, i.e. one core supports instructions the other doesn't, unless this information is available to the scheduler, there's no way it can make that decision. AVX512 was such an example, and sadly it ended up getting locked off from the P cores.
- wutwutwat 3y agoSomething made the decision if it got "locked off from the P cores", what was it if not the OS scheduler?
- wtallis 3y agoWhat got locked off was the P-core's AVX512 instruction support, not some process's core affinity. Intel didn't have an E-core design ready to support AVX512 in Alder Lake. They initially allowed AVX512 to be enabled on the P-cores if all the E-cores were disabled at boot, but they later switched to fusing off AVX512 support permanently.
- wutwutwat 3y agoInteresting, but what does this have to do with what my original comment was about?