On 09/17/2014 08:23 PM, Kevin Easton wrote: > I was actually thinking that the kernel would take care of the xsave / > xrstor (for current), updating tsk->thread.fpu.state (for non-running > threads) and sending an IPI for threads running on other CPUs. > > Of course userspace can always then manually change the bounds directory > address itself, but then it's quite clear that they're doing something > unsupported. Just an idea, anyway. What's the benefit of that? As it stands now, MPX is likely to be enabled well before any threads are created, and the MPX enabling state will be inherited by the new thread at clone() time. The current mechanism allows a thread to individually enable or disable MPX independently of the other threads. I think it makes it both more complicated and less flexible. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>