14 Apr
2014
14 Apr
'14
12:06 p.m.
On Mon, Apr 14, 2014 at 05:22:30PM +0530, Viresh Kumar wrote:
On 14 April 2014 17:17, Peter Zijlstra peterz@infradead.org wrote:
What causes this tick? I was under the impression that once there's a single task (not doing any syscalls) and the above issues are sorted, no more tick would happen.
This is what Frederic told me earlier:
That's a bit of a non-answer. I'm fairly sure its not a gazillion issues, since the actual scheduler tick doesn't actually do that much.
So start by enumerating what is actually required.
The 2), which I suppose you're now trying to implement is I think entirely the wrong way. The tick really assumes it runs local, moving it to another CPU is insane.