The Linaro Connect scheduler minisummit

having userspace decide when to start/stop cores makes sense to me (but apparantly others disagree), but once userspace has made cores available to the system, having to have it evaluate which cores a process can run on continually seems like a bad idea.

It's common for a process that's frequently a CPU hog to have times when it's not, and in any case, having a CPU hog not running because the 'fast' cores are all busy when a 'slow' core is idle is a bad idea.

so 'fixing' this problem by relying on userspace to set/adjust affinity settings doesn't seem workable.