> How will the software know to not move the thread to the efficiency core?
There could be a dirty state flag that indicates whether vector registers or other advanced instructions were used.
> If it did do so wouldn't it throw errors?
The kernel could catch those errors and move the thread back to the performance core and resume execution at the trapped instruction and mark the thread as non-schedulable on the efficiency cores.
There could be a dirty state flag that indicates whether vector registers or other advanced instructions were used.
> If it did do so wouldn't it throw errors?
The kernel could catch those errors and move the thread back to the performance core and resume execution at the trapped instruction and mark the thread as non-schedulable on the efficiency cores.