Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757476AbYJPVFn (ORCPT ); Thu, 16 Oct 2008 17:05:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754708AbYJPVFf (ORCPT ); Thu, 16 Oct 2008 17:05:35 -0400 Received: from mx1.redhat.com ([66.187.233.31]:35055 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755139AbYJPVFe (ORCPT ); Thu, 16 Oct 2008 17:05:34 -0400 Date: Thu, 16 Oct 2008 17:04:30 -0400 From: Jason Baron To: linux-kernel@vger.kernel.org Cc: compudj@krystal.dyndns.org, fche@redhat.com, fweisbec@gmail.com, edwintorok@gmail.com, mingo@elte.hu, peterz@infradead.org Subject: tracepoints for kernel/mutex.c Message-ID: <20081016210430.GC25738@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5273 Lines: 188 hi, Below are 3 tracepoints I've been playing with in kernel/mutex.c using a SystemTap script. The idea is to detect and determine the cause of lock contention. Currently I get the following output: