From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21457 invoked by alias); 30 Apr 2009 18:00:09 -0000 Received: (qmail 21448 invoked by uid 22791); 30 Apr 2009 18:00:07 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Apr 2009 18:00:02 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n3UI00iG019095; Thu, 30 Apr 2009 14:00:00 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n3UHxx40017731; Thu, 30 Apr 2009 13:59:59 -0400 Received: from localhost.localdomain (dst61.hsv.redhat.com [172.16.16.175]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n3UHxvs9016767; Thu, 30 Apr 2009 13:59:58 -0400 Message-ID: <49F9E71D.2070500@redhat.com> Date: Thu, 30 Apr 2009 18:00:00 -0000 From: David Smith User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Maynard Johnson CC: systemtap@sourceware.org, "Frank Ch. Eigler" , Roland McGrath Subject: Re: Backward compatibility for insn probe point References: <49D3E3DF.1000108@us.ibm.com> <49F61D09.8090503@redhat.com> <49F8C1C0.8070208@us.ibm.com> In-Reply-To: <49F8C1C0.8070208@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2009-q2/txt/msg00487.txt.bz2 Maynard Johnson wrote: > David Smith wrote: >> Maynard Johnson wrote: ... stuff deleted ... >>> The result of the above test is that the stap command hangs at >>> "stapio:start_cmd:195 execing target_cmd /bin/ls". If I Ctl-C the >>> job, it finished (i.e, I see "Pass 5: run completed ..."), but the >>> output file contents indicate the insn probe was not hit (i.e., >>> "itraced = 0"). >>> >>> Any suggestions on where to look for the problem? >> I took a look at this and fixed it. For more details, see > I've not tested the fix on x86 yet, but I'm afraid the results don't look right on ppc64/RHEL 5. > But test results of 0.9.7 with your patch on ppc64/F11 were good -- no regressions. I used the > following simple test script: ... script deleted ... > I invoked the script as follows: > stap -c /usr/bin/whoami simple-test.stp /usr/bin/whoami -o simple-out > On Fedora 11, the simple-out file showed that I had nearly 330,000 insn probe hits. On ppc64/RHEL > 5.3, I had only 65 probe hits. Can you try out the above script on an x86/RHEL 5.3 system? I've tested this on x86/RHEL5.3 (2.6.18-128.1.6.el5) and I get 226127 probe hits. On x86_64/RHEL5.3 (2.6.18-128.1.6.el5) I get 198294 probe hits. Off the top of my head that might mean there is a specific ppc64 utrace problem. Roland, do you know of any problems with original utrace doing UTRACE_ACTION_SINGLESTEP on ppc64? -- David Smith dsmith@redhat.com Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)