From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5950 invoked by alias); 3 Apr 2006 09:06:16 -0000 Received: (qmail 5933 invoked by uid 22791); 3 Apr 2006 09:06:16 -0000 X-Spam-Status: No, hits=-1.5 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 09:06:14 +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 k339Ex61165782 for ; Mon, 3 Apr 2006 19:15:00 +1000 Received: from d23av02.au.ibm.com (d23av02.au.ibm.com [9.190.250.243]) by sd0208e0.au.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k3399G21238542 for ; Mon, 3 Apr 2006 19:09:26 +1000 Received: from d23av02.au.ibm.com (loopback [127.0.0.1]) by d23av02.au.ibm.com (8.12.11/8.13.3) with ESMTP id k3395vWl018422 for ; Mon, 3 Apr 2006 19:05:57 +1000 Received: from [127.0.0.1] ([9.181.133.58]) by d23av02.au.ibm.com (8.12.11/8.12.11) with ESMTP id k3395l7V018104; Mon, 3 Apr 2006 19:05:54 +1000 Message-ID: <4430E569.8050904@cn.ibm.com> Date: Mon, 03 Apr 2006 09:06:00 -0000 From: Li Guanglei Organization: IBM CSTL User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "Mao, Bibo" CC: systemtap Subject: Re: patch for module function probe References: <9FBCE015AF479F46B3B410499F3AE05BEDA977@pdsmsx405> In-Reply-To: <9FBCE015AF479F46B3B410499F3AE05BEDA977@pdsmsx405> 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: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q2/txt/msg00008.txt.bz2 Mao, Bibo : > Hi, > Currently systemtap has some problem when searching module > function, which is reported in > http://sourceware.org/ml/systemtap/2006-q1/msg00674.html. Kernel is > treated as one module whose name is TOK_KERNEL "kernel". So this script > will pass to compile, it indeed will probe kernel function: > probe module("kernel").function("sys_read"){ > } > But there will be problem when there is actually one module named > kernel.ko though its name is weird. > > Bibo,mao > Actually, I think the expansion of module("*").function("foo") into kernel.function("foo") is a designed feature. It is especially useful for those compiled-in kernel modules. For example, in LKET, I can use: probe addevent.scsi.iodispatching = module("*").function("scsi_dispatch_cmd@drivers/scsi/scsi.c") to let LKET work despite scsi_mod being compiled as a module or into the kernel.