public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org, arjan@infradead.org
Subject: Re: locking hierarchy based on lockdep
Date: Mon, 6 Nov 2006 21:05:29 +0100	[thread overview]
Message-ID: <20061106200529.GA15370@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0611061315380.29750@dhcp83-20.boston.redhat.com>


* Jason Baron <jbaron@redhat.com> wrote:

> I've implemented this as a /proc file, but Ingo suggested that it 
> might be better for us to simply produce an adjaceny list, and then 
> generate a locking hierarchy or anything else of interest off of that 
> list.... [...]

this would certainly be the simplest thing to do - we could extend 
/proc/lockdep with the list of 'immediately after' locks separated by 
commas. (that list already exists: it's the lock_class.locks_after list)

i like your idea of using lockdep to document locking hierarchies.

	Ingo

  reply	other threads:[~2006-11-06 20:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 18:32 locking hierarchy based on lockdep Jason Baron
2006-11-06 20:05 ` Ingo Molnar [this message]
2006-11-06 20:21   ` Roland Dreier
2006-11-06 20:22     ` Jason Baron
2006-11-06 20:37       ` Roland Dreier
2006-11-06 20:40         ` Jason Baron
2006-11-07 23:39   ` Jason Baron
2006-11-07 23:53     ` Ingo Molnar
2006-11-08 18:04       ` Jason Baron
2006-11-09  9:15         ` Ingo Molnar
2006-11-09 18:58           ` Jason Baron
2006-11-10  9:27             ` Ingo Molnar
2006-11-08 13:08     ` Pavel Machek

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=20061106200529.GA15370@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox