Re: locking hierarchy based on lockdep

[Ingo Molnar]

* Jason Baron <jbaron@xxxxxxxxxx> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/