From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-2932-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 18783 invoked by alias); 3 Apr 2006 09:25:57 -0000
Received: (qmail 18773 invoked by uid 22791); 3 Apr 2006 09:25:55 -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 09:25:53 +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 k339YffL060702 	for <systemtap@sources.redhat.com>; Mon, 3 Apr 2006 19:34:41 +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 k339T721233210 	for <systemtap@sources.redhat.com>; Mon, 3 Apr 2006 19:29:07 +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 k339PmVR020062 	for <systemtap@sources.redhat.com>; Mon, 3 Apr 2006 19:25:48 +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 k339Pf0c019904 	for <systemtap@sources.redhat.com>; Mon, 3 Apr 2006 19:25:45 +1000
Message-ID: <4430EA16.8020702@cn.ibm.com>
Date: Mon, 03 Apr 2006 09:25:00 -0000
From: Li Guanglei <guanglei@cn.ibm.com>
Organization: IBM CSTL
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: adding statements in alias definition as epilogue
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/msg00010.txt.bz2

Currently the statement block that follows an alias definition is 
implicitly added as a prologue to any probe that refers to the alias. 
But it seems to me that only allowing adding those statements 
contained in an alias definition as a prologue makes me to lose some 
controls over them.

For example, I have a tapsets:

probe addevent.tskdispatch.cpuidle
         = kernel.inline("idle_balance")
{
         log_cpuidle_tracedata(HOOKID_TASK_CPUIDLE, backtrace)
}

What I want is to let user specify whether to log backtrace in his 
scripts, like the following:

stap -e "probe addevent.tskdispatch.cpuidle { backtrace=1 } -I 
LKET_TAPSETS

But unfortunately, it won't work because "backtrace=1" is added after 
"log_cpuidle_tracedata(HOOKID_TASK_CPUIDLE, backtrace)". So how about 
providing a way to specify whether the statements in a alias 
definition could be added as prologue or epilogue to any probe that 
refers to that alias?