From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14515 invoked by alias); 18 Jul 2011 14:13:00 -0000 Received: (qmail 14508 invoked by uid 22791); 18 Jul 2011 14:12:59 -0000 X-SWARE-Spam-Status: No, hits=-6.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS 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, 18 Jul 2011 14:12:28 +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 p6IECQHY005274 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 18 Jul 2011 10:12:26 -0400 Received: from [10.11.231.236] (deploy7.rdu.redhat.com [10.11.231.236]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p6IECPmL030913; Mon, 18 Jul 2011 10:12:26 -0400 Message-ID: <4E243F49.9020706@redhat.com> Date: Mon, 18 Jul 2011 14:13:00 -0000 From: William Cohen User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Red Hat/3.1.11-2.el6_1 Thunderbird/3.1.11 MIME-Version: 1.0 To: "Turgis, Frederic" CC: Da Zheng , "systemtap@sourceware.org" Subject: Re: error to run systemtap in an ARM platform References: <4E1F90A8.2080000@gmail.com> <1310722941.4510.5.camel@springer.wildebeest.org> <4E209C3F.6060806@gmail.com> <4E20A6EF.9010003@redhat.com> <4E20B11A.5020402@gmail.com> <13872098A06B02418CF379A158C0F1460162204601@dnce02.ent.ti.com> In-Reply-To: <13872098A06B02418CF379A158C0F1460162204601@dnce02.ent.ti.com> Content-Type: text/plain; charset=windows-1252 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: 2011-q3/txt/msg00041.txt.bz2 On 07/15/2011 08:22 PM, Turgis, Frederic wrote: > Hi, > > We are making quite good use of systemtap here at TI and try to expand to more teams internally. We use it both through cross and native compilation. We have leveraged mostly v1.3 but we are planning to move to v1.5 > > - for your "probe syscalls.*" issue, I can tell it was working with v1.3 (we use sometimes syscalls_by_pid.stp example) with some instability at execution in few cases. Since then, sycalls.stp and syscalls2.stp have evolved and contain some architecture specific code. If you can't port it (which shall be the way to go), you can try to revert the commits. OK, not clean but a way to move forward if you really need this. > > - http://sourceware.org/systemtap/wiki/SystemtapOnFedoraArm mentions http://omappedia.org/wiki/Systemtap, which corresponds to our experiments on Android, i.e. cross-compilation. Still fedora page is very complet and probably suits you best, use OMAP page as a complement > > - https://wiki.linaro.org/Platform/DevPlatform/systemtap is also interesting in its short intro to systemtap and what we require in terms of debug symbols, kernel config... in context of Linaro (i.e. ARM). Some thoughts also about timestamping events and a list of issues discovered when running testsuite on v1.3 (you can see it in mail archive, look for my e-mail) > > We don't have a huge community yet on ARM but most of the people whom we show the tool (even customers) recognize the benefits of it and somehow leverage it > > Regards > Fred > > Frederic Turgis > OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement > > Hi Turgis, Thanks for the SystemTap page on http://omappedia.org/wiki/Systemtap it was very good starting point for me. I wasn't aware of https://wiki.linaro.org/Platform/DevPlatform/systemtap. Both http://omappedia.org/wiki/Systemtap and https://wiki.linaro.org/Platform/DevPlatform/systemtap mention high resolution timers being something missing. For some of the issues listed on the pages it would good idea to put feature requests to see if some of these could be addressed for arm. -Will