* Peter Zijlstra <[email protected]> wrote:
> On Wed, 2013-04-10 at 13:06 +0200, Ingo Molnar wrote:
>
> > There's just a handful of high level entry points, right? schedule(),
> > wakeup,
> > scheduler tick, maybe notifiers - anything else?
>
> I suppose there's some cgroup muck and the various system calls; most
> of them should be covered if we take some lower level primitives or so.
>
> We could 'simply' hijack rq->lock and clear the state every time we
> acquire or release it.. maybe have an exemption for the balance double
> lock ops.
That would be feasible ...
Thanks,
Ingo
--
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/
