On 2019-03-12 17:06:18 [-0700], Dave Hansen wrote: > Thanks for doing this. I'll see if I can dig into the test case and > figure out why it's not doing what I expected. It might be that the CPU > _could_ go back to the init state but chooses not to, or that something > else is taking us out of the init state before we reach the kernel code > in question. I'm going to drop that WARN_ON() check. The reason is that we are fully preemptible during fpstate_init() and a context switch during memset() and fpstate_init_xstate() triggers this warning. Sebastian
