On Thu, Jun 11, 2015 at 12:02:45PM +0800, Chunyan Zhang wrote: > From: Janet Liu <janet....@spreadtrum.com> > > Now FPSIMD don't handle HOTPLUG_CPU. This introduces bug after cpu down/up > process. > > After cpu down/up process, the FPSMID hardware register is default value, not > any > process's fpsimd context. when CPU_DEAD set cpu's fpsimd_state to NULL, it > will force > to load the fpsimd context for the thread, to avoid the chance to skip to > load the context. > If process A is the last user process on CPU N before cpu down, and the first > user process > on the same CPU N after cpu up, A's fpsimd_state.cpu is the current cpu id, > and per_cpu(fpsimd_last_state) points A's fpsimd_state, so kernel will not > reload the > context during it return to user space. > > Signed-off-by: Janet Liu <janet....@spreadtrum.com> > Signed-off-by: Xiongshan An <xiongshan...@spreadtrum.com> > Signed-off-by: Chunyan Zhang <chunyan.zh...@spreadtrum.com>
Applied. Thanks. -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
