15 Jan
2014
15 Jan
'14
11:34 a.m.
On Wed, Jan 15, 2014 at 04:17:26PM +0530, Viresh Kumar wrote:
On 15 January 2014 16:08, Peter Zijlstra peterz@infradead.org 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.
We should have a cpuset.quiesce control or something that moves all timers out.
And then there were timer overflow events that occur because hrtimer is started by tick-sched stuff for 450 seconds later in time.
-ENOPARSE