* Peter Zijlstra <[email protected]> wrote:
> On Thu, Nov 08, 2018 at 07:32:46AM +0100, Ingo Molnar wrote: > > > > * Aubrey Li <[email protected]> wrote: > > > > > Expose the per-task cpu specific thread state value, it's helpful > > > for userland to classify and schedule the tasks by different policies > > > > That's pretty vague - what exactly would use this information? I'm sure > > you have a usecase in mind - could you please describe it? > > Yeah, "thread_state" is a pretty terrible name for this. The use-case is > detectoring which tasks use AVX3 such that a userspace component (think > job scheduler) can cluster them together. I'd prefer the kernel to do such clustering... Thanks, Ingo
