From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Lock dependency based tree report in perf lock
Date: Sat, 30 Jan 2010 19:57:37 +0100 [thread overview]
Message-ID: <20100130185736.GC5675@nowhere> (raw)
In-Reply-To: <1264841188.24455.54.camel@laptop>
On Sat, Jan 30, 2010 at 09:46:28AM +0100, Peter Zijlstra wrote:
> On Sat, 2010-01-30 at 00:17 +0100, Frederic Weisbecker wrote:
> >
> >
> > Anyway, that's just an idea, not trivial I must admit.
>
> lockdep actually collects all this information, so writing it out isn't
> too hard.
Lockdep collects the theorical dependencies but not the practical
scenarios.
Say B and C depend on A, you'll get:
A
/ \
B C
But nothing can tell you that if A is taken, B and C will always
be taken. You may have different scenarios based on this dependency,
which is not something that lockdep logs, right?
next prev parent reply other threads:[~2010-01-30 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 23:17 Lock dependency based tree report in perf lock Frederic Weisbecker
2010-01-30 8:46 ` Peter Zijlstra
2010-01-30 18:57 ` Frederic Weisbecker [this message]
2010-02-01 8:25 ` Peter Zijlstra
2010-02-01 17:48 ` Frederic Weisbecker
2010-02-01 1:23 ` Frederic Weisbecker
2010-02-01 9:21 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100130185736.GC5675@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.