3 ms·
I doubt that any CPU manufacturer is going to go first in crippling its memory subsystem. I think realistically the only safe and not completely performance cr
by gpderetta 9y ago
I doubt that any CPU manufacturer is going to go first in crippling its memory subsystem.
I think realistically the only safe and not completely performance crippling workaround will be, at the very least, to run any untrusted code under a separate address space (assuming that the cpu is immune from meltdown). That doesn't necessarily require a full blown separate process, but something like memory protection keys might work.
The alternative is full static analysis and source level annotations, which realistically is only going to be done for very few programs and will still be error prone.
- DannyBee 9y agoYeah, i don't disagree at all. Something like this what i meant by "cooperation" (lfence or equivalent for code that can't be isolated but must be protected) + "weird abstractions" (IE back to segmented land we go)
- gpderetta 9y agoForgot about segments! Time to resurrect them on x86-64 cpus?