Date: Fri, 13 Nov 2009 13:21:25 +0900 (JST)
Message-Id: <20091113.132125.468378199533086916.mitake@dcl.info.waseda.ac.jp>
To: mingo@elte.hu
Cc: a.p.zijlstra@chello.nl, tglx@linutronix.de, fweisbec@gmail.com,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Measuring term of acquiring spinlock
From: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
In-Reply-To: <20091112073909.GB31719@elte.hu>
References: <20091112.154353.680961628170545165.mitake@dcl.info.waseda.ac.jp>
	<20091112073909.GB31719@elte.hu>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1039
Lines: 29

From: Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH][RFC] Measuring term of acquiring spinlock
Date: Thu, 12 Nov 2009 08:39:09 +0100

> 
> * Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> wrote:
> 
> > * Description
> > 
> > This patch makes the file spinlock_stats on top of the debugfs.
> > When user reads this file, some statistical data related to
> > spinlocks are printed.
> 
> hm, are you aware of the lockstat tracepoints? They do something like 
> this - and it utilizes perf events to report these events. See 
> include/trace/events/lockdep.h. Needs CONFIG_LOCK_STAT enabled.
>

Wow, I didn't know that. I'll try it.

> Might make sense to put it into 'perf lock' kind of tool. I think 
> Frederic had such plans.

If you want a tester for 'perf lock', please call me, Frederic :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/