* Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-03-22 at 07:57 +0100, Jarek Poplawski wrote:
> > And here is some addition.
> >
> > [PATCH] lockdep: debug_show_all_locks & debug_show_held_locks vs.
> > debug_locks
> >
> > lockd
On Thu, 2007-03-22 at 07:57 +0100, Jarek Poplawski wrote:
> And here is some addition.
>
> [PATCH] lockdep: debug_show_all_locks & debug_show_held_locks vs. debug_locks
>
> lockdep's data shouldn't be used when debug_locks == 0
> because it's not updated after this, s
On Thu, 2007-03-22 at 07:57 +0100, Jarek Poplawski wrote:
And here is some addition.
[PATCH] lockdep: debug_show_all_locks debug_show_held_locks vs. debug_locks
lockdep's data shouldn't be used when debug_locks == 0
because it's not updated after this, so it's more misleading
than
* Peter Zijlstra [EMAIL PROTECTED] wrote:
On Thu, 2007-03-22 at 07:57 +0100, Jarek Poplawski wrote:
And here is some addition.
[PATCH] lockdep: debug_show_all_locks debug_show_held_locks vs.
debug_locks
lockdep's data shouldn't be used when debug_locks == 0
because it's
And here is some addition.
[PATCH] lockdep: debug_show_all_locks & debug_show_held_locks vs. debug_locks
lockdep's data shouldn't be used when debug_locks == 0
because it's not updated after this, so it's more misleading
than helpful.
PS: probably lockdep's current-> fields should b
And here is some addition.
[PATCH] lockdep: debug_show_all_locks debug_show_held_locks vs. debug_locks
lockdep's data shouldn't be used when debug_locks == 0
because it's not updated after this, so it's more misleading
than helpful.
PS: probably lockdep's current- fields should be reset
6 matches
Mail list logo