Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758261AbYHDCL2 (ORCPT ); Sun, 3 Aug 2008 22:11:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753892AbYHDCLU (ORCPT ); Sun, 3 Aug 2008 22:11:20 -0400 Received: from fk-out-0910.google.com ([209.85.128.184]:40646 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753861AbYHDCLT (ORCPT ); Sun, 3 Aug 2008 22:11:19 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=RzyHTdlJGoOJdAlQqI9Rnz9ti3AI1+IU/JPerDNxpate7f8uiH2GwP5REE3rsYuz9q MoLp3oXAxPfJIChN3GsHdj5+s5bj2sp3CpPwLUbGSNTYQAY/qYADrrpijAOttu2J0IEL DmZjogGFtGjP3Ao83zNbbWVQa2cqdNLFvTx/o= Message-ID: Date: Mon, 4 Aug 2008 10:11:17 +0800 From: "Ming Lei" To: "Steven Rostedt" Subject: Re: [RFC] ftrace: support tracing functions in one module Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" , "Andrew Morton" , "Steven Rostedt" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1495 Lines: 46 2008/8/3 Steven Rostedt : > > On Sun, 3 Aug 2008, Ming Lei wrote: > >> Hi, >> >> IMO, ftrace is a very good tools, which can monitor almost all >> functions calling >> in the running kernel. The traced result is very complete and intact. >> But it seems >> too large to grasp the interested content. For example, one may only >> have interest in >> functions calling in usbcore.ko, but he must trace all the functions >> calling in the >> kernel, so the tracing result is too large to use it. >> >> Could you add the support of tracing functions in one module only to ftrace? > > Look at the set_ftrace_filter in ftrace.txt. You can pick and choose which > functions to trace. All the functions that can be traced is in It seems not ver easy to opearte to trace all functions in a module. You need to write all function names to set_ftrace_filter. Also some functions have same names in kernel and modules. This can lead to some messed trace result. Do you have the plan to support tracing functions in one module or in one kernel address range? > available_filter_functions in the debugfs/tracing directory. > > Note, the functions must execute at least once before they can be > recorded. > > -- Steve > > -- Lei Ming -- 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/