From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755191AbYHPBq6 (ORCPT ); Fri, 15 Aug 2008 21:46:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753175AbYHPBqt (ORCPT ); Fri, 15 Aug 2008 21:46:49 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.125]:56607 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752944AbYHPBqt (ORCPT ); Fri, 15 Aug 2008 21:46:49 -0400 Message-Id: <20080816014003.978160137@goodmis.org> User-Agent: quilt/0.46-1 Date: Fri, 15 Aug 2008 21:40:03 -0400 From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: Ingo Molnar , Thomas Gleixner , Peter Zijlstra , Andrew Morton , Linus Torvalds , David Miller Subject: [PATCH 0/2] ftrace updates Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Due to the new mcount recording method, the assumptions about the records that hold the mcount locations have changed. Now we need to protect reading and writing of the records between module load and reading of the debugfs files. There is not much contention here, but they need to be protected none the less. I simply use the ftrace_lock to accomplish this. The ftrace_lock should never be held under interrupt context so disabling interrupts should not be necessary. I've run this under lockdep and lockdep has not complained. -- Steve