Hacker News new | past | comments | ask | show | jobs | submit login

Maybe I'm dumb and for sure I'm not an expert of this subject but wouldn't we need an executable containing both an AVX512 code path and an alternative plain code one, plus a way to switch code paths according to the core the code is running on? The same memory page would run in a P core or in an E core. Inefficient because of the extra checks?



userspace can be preempted at any instruction, so you have a TOCTOU problem.


Sure, but one can first pin the thread to a core, or a "don't move me between core types" flag could be added to OSes.


Right, thanks.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: