From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3320 invoked by alias); 11 Apr 2011 17:40:56 -0000 Received: (qmail 3304 invoked by uid 22791); 11 Apr 2011 17:40:55 -0000 X-SWARE-Spam-Status: No, hits=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 11 Apr 2011 17:40:46 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p3BHeXoC031798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 11 Apr 2011 13:40:44 -0400 Received: from fche.csb (vpn-11-215.rdu.redhat.com [10.11.11.215]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p3BGqr61024380; Mon, 11 Apr 2011 12:52:54 -0400 Received: by fche.csb (Postfix, from userid 2569) id 3D7EA58156; Mon, 11 Apr 2011 12:52:53 -0400 (EDT) To: voyager1983 Cc: systemtap@sourceware.org Subject: Re: Can kernel.statement access the function argument? References: <31348406.post@talk.nabble.com> <4D9F2EE3.3020505@redhat.com> <31356706.post@talk.nabble.com> From: fche@redhat.com (Frank Ch. Eigler) Date: Mon, 11 Apr 2011 17:40:00 -0000 In-Reply-To: <31356706.post@talk.nabble.com> (wang.yongzhi2009@gmail.com's message of "Fri, 8 Apr 2011 17:37:34 -0700 (PDT)") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2011-q2/txt/msg00067.txt.bz2 voyager1983 writes: > What I am about to probe is actually the statement > ret = action->handler(irq, action->dev_id); > [...] > stap -L 'kernel.statement("handle_IRQ_event@kernel/irq/handle.c:376")' > It returns nothing. That's partly because the handle_IRQ_event function is blacklisted due to some historical incompatibility with kernel kprobes. You may try again with stap -g ... - FChE