From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-2935-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 28218 invoked by alias); 3 Apr 2006 10:03:52 -0000
Received: (qmail 28211 invoked by uid 22791); 3 Apr 2006 10:03:52 -0000
X-Spam-Status: No, hits=-1.6 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from ausmtp04.au.ibm.com (HELO ausmtp04.au.ibm.com) (202.81.18.152)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 03 Apr 2006 10:03:50 +0000
Received: from sd0208e0.au.ibm.com (d23rh904.au.ibm.com [202.81.18.202]) 	by ausmtp04.au.ibm.com (8.13.6/8.13.5) with ESMTP id k33ACad4192604 	for <systemtap@sources.redhat.com>; Mon, 3 Apr 2006 20:12:38 +1000
Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [9.190.250.237]) 	by sd0208e0.au.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k33A7221241492 	for <systemtap@sources.redhat.com>; Mon, 3 Apr 2006 20:07:02 +1000
Received: from d23av04.au.ibm.com (loopback [127.0.0.1]) 	by d23av04.au.ibm.com (8.12.11/8.13.3) with ESMTP id k33A3h6b032234 	for <systemtap@sources.redhat.com>; Mon, 3 Apr 2006 20:03:43 +1000
Received: from [127.0.0.1] ([9.181.133.58]) 	by d23av04.au.ibm.com (8.12.11/8.12.11) with ESMTP id k33A3W1A031813; 	Mon, 3 Apr 2006 20:03:39 +1000
Message-ID: <4430F2F6.4010402@cn.ibm.com>
Date: Mon, 03 Apr 2006 10:03:00 -0000
From: Li Guanglei <guanglei@cn.ibm.com>
Organization: IBM CSTL
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: bibo mao <bibo_mao@linux.intel.com>
CC: "Mao, Bibo" <bibo.mao@intel.com>, systemtap <systemtap@sources.redhat.com>
Subject: Re: patch for module function probe
References: <9FBCE015AF479F46B3B410499F3AE05BEDA977@pdsmsx405> <4430E569.8050904@cn.ibm.com> <4430E75E.5090204@linux.intel.com>
In-Reply-To: <4430E75E.5090204@linux.intel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2006-q2/txt/msg00013.txt.bz2

bibo mao :
> If it is designed feature, then kernel.function("foo") will be regarded 
> as module("kernel").function("foo").  But if there is one module named 
> "kernel.ko", how to probe its function although its module name is 
> weird?  In another way to say what is the meaning of 
> module("kernel").function("foo"), else stap manual clarify that 
> module("kernel") means kernel image, user had better not use the same 
> module name.

I tried and found:
module("kernel").function("foo") == kernel.function("foo"), which 
seems not appropriate.

I once thought module("*").function("foo") would be expanded as:
   module("aaa").function("foo")
   module("bbb").function("foo")
   module("kernel").function("foo")  // if happened to have a module 
named module which also has a function named foo
   ...
   kernel.function("foo")

That is to day, it should first search all loaded modules for function 
foo, then at last it will also search kernel image for function foo. 
So we need to change the current way it works with module("*").