From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753169AbWKFUFz (ORCPT ); Mon, 6 Nov 2006 15:05:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753177AbWKFUFz (ORCPT ); Mon, 6 Nov 2006 15:05:55 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:46990 "EHLO mx2.mail.elte.hu") by vger.kernel.org with ESMTP id S1753169AbWKFUFy (ORCPT ); Mon, 6 Nov 2006 15:05:54 -0500 Date: Mon, 6 Nov 2006 21:05:29 +0100 From: Ingo Molnar To: Jason Baron Cc: linux-kernel@vger.kernel.org, arjan@infradead.org Subject: Re: locking hierarchy based on lockdep Message-ID: <20061106200529.GA15370@elte.hu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-ELTE-SpamScore: -2.8 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.8 required=5.9 tests=ALL_TRUSTED,AWL,BAYES_50 autolearn=no SpamAssassin version=3.0.3 -3.3 ALL_TRUSTED Did not pass through any untrusted hosts 0.5 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.5000] -0.0 AWL AWL: From: address is in the auto white-list X-ELTE-VirusStatus: clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Jason Baron 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