Presumably you could safely HT threads of the same process?
If you do that I don't think it's resumeable. You would rather spin on a variable "while(sibling core is in kernel)" then ret-to-user. You also need to multiplex IPI with other kernel use of it, which brings in nontrivial kernel surface.
-
-
And somebody would signal() the HT while the other thing was in kernel and run exploit code in the handler... Needs HW support.
-
No, signals can't interrupt kernelspace except voluntarily via EINTR/restart. They're handled on return from kernel to user.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.