3 ms·
I'd like to see CPU's having a notion of "theoretical time" and "real time". Theoretical time ticks once per CPU instruction or similar. Real time is kept in
by londons_explore 6y ago
I'd like to see CPU's having a notion of "theoretical time" and "real time". Theoretical time ticks once per CPU instruction or similar. Real time is kept in sync with theoretical time by slowing the CPU down if theoretical time gets ahead, and throwing an exception if real time gets ahead.
All IO with untrusted devices would be delayed until the real time exceeds the theoretical time the message was sent.
Then one can have as many timing sidechannels as one likes, and the running program can never learn about them.
- GregarianChild 6y agoThat would be great. But isn't there a danger, that such a CPU, at least if implemented naievely, would basically mostly idle, since modern OoO processors schedule memory access dynamically? For hard real-time tasks, some CPUs don't have caches, to make timing more predictable, but there is a heavy performance penalty to be paid for that predictability. Are you familiar with works like [1]? That is thinking in this direction, but from a different angle. [1] G. Heiser, G. Klein, T. Murray, Can We Prove Time Protection?. https://arxiv.org/pdf/1901.08338.pdf https://arxiv.org/pdf/1901.08338.pdf
- sitkack 6y ago> heavy performance penalty to be paid for that predictability I think this is probably a fascinating area of study. It feels like there is a power/time/space non-linearity and being able to trade one for another. How about the CPU is put into a fixed timestep mode, where all operations take the same amount of time. If there was a hardware level concept of a thread, it could be a thread property. Another option would be a queue of futures with a rate control based on the required security properties.