3 ms·
How can the registers still hold this info when users switch? I would think that it is very transitory, and wiped by other stuff quickly
by EGreg 3y ago
How can the registers still hold this info when users switch? I would think that it is very transitory, and wiped by other stuff quickly
- CanaryLayout 3y agoThe OS job scheduler informs the CPU when it's ideal to swap jobs. But the OS is not doing the work of moving the register and stack pointers, the microcode is. These timing attacks take advantage of shared information in the cache (where it's likely the context of the thread you are not supposed to be able to read is). SMT (hyperthreading) introduces some ambiguity when the context change is going to happen, and it appears there's instructions that are callable where registers/mem can be read that were outside the calling context.