On Fri, Jun 07, 2019 at 12:32:23PM -0700, Andy Lutomirski wrote: > Sigh. > > It seems silly to add a workaround for a language that has trouble > calling somewhat-but-not-too-slow syscalls or ioctls. > > How about fixing this in Go directly? Either convince the golang > people to add a way to allocate a real thread for a particular region > of code or have the Go SGX folks write a bit of C code to do a whole > bunch of ioctls and have Go call *that*. Then the mess stays in Go > where it belongs. A worker thread would be only appropriate if the existing SGX code was already in the mainline because then it would break the user space. Doing it either way right now does not break anything so there is no case for having it. /Jarkko
