Announcement
Collapse
No announcement yet.
Kernel Address Space Isolation Aims To Prevent Leaking Data From Hyper Threading Attacks
Collapse
X
-
Originally posted by coder View PostWell, of course there'd be a performance cost, but at least it should be better than completely disabling HT!
I read an article (I think on Phoronix) were some hyper-threading mitigations attempts were worse than just disabling hyper threading.
It's a crazy world where programmers intentionally throw out CPU cache and pile extra work into context switching.
- Likes 1
Comment
-
Originally posted by JEBjames View PostI read an article (I think on Phoronix) were some hyper-threading mitigations attempts were worse than just disabling hyper threading.
One beef I have with thread scheduling is that I'm not aware of an API for telling the kernel which threads are involved in high-bandwidth or require low-latency communication with each other. That, and I should be able to define thread sets with different compute characteristics, so the scheduler can know which threads it can pair up nicely. I've been down the road of manually setting thread affinity, but that places too much burden on the programmer and really over-specifies the constraints.
I'm a fan of the way OpenCL's approach to the first problem, although the second problem doesn't apply so much to OpenCL.
Comment
Comment