On 15 January 2014 16:08, Peter Zijlstra <[email protected]> wrote: > Nah, its just ugly and we should fix it. You need to be careful to not > place tasks in a cpuset you're going to unplug though, that'll give > funny results.
Okay. So how do you suggest to get rid of cases like a work queued on CPU1 initially and because it gets queued again from its work handler, it stays on the same CPU forever. And then there were timer overflow events that occur because hrtimer is started by tick-sched stuff for 450 seconds later in time. -- viresh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
