From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4251 invoked by alias); 19 Jul 2011 11:38:09 -0000 Received: (qmail 4239 invoked by uid 22791); 19 Jul 2011 11:38:08 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,LOTS_OF_MONEY,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from bear.ext.ti.com (HELO bear.ext.ti.com) (192.94.94.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 19 Jul 2011 11:37:53 +0000 Received: from dlep34.itg.ti.com ([157.170.170.115]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id p6JBbhUb026607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jul 2011 06:37:43 -0500 Received: from dlep26.itg.ti.com (smtp-le.itg.ti.com [157.170.170.27]) by dlep34.itg.ti.com (8.13.7/8.13.8) with ESMTP id p6JBbgeA021672; Tue, 19 Jul 2011 06:37:43 -0500 (CDT) Received: from dnce72.ent.ti.com (localhost [127.0.0.1]) by dlep26.itg.ti.com (8.13.8/8.13.8) with ESMTP id p6JBbgQd008401; Tue, 19 Jul 2011 06:37:42 -0500 (CDT) Received: from dnce02.ent.ti.com ([137.167.131.106]) by dnce72.ent.ti.com ([137.167.131.87]) with mapi; Tue, 19 Jul 2011 13:37:41 +0200 From: "Turgis, Frederic" To: William Cohen , "Frank Ch. Eigler" CC: Da Zheng , "systemtap@sourceware.org" Content-Class: urn:content-classes:message Date: Tue, 19 Jul 2011 11:38:00 -0000 Subject: RE: error to run systemtap in an ARM platform Message-ID: <13872098A06B02418CF379A158C0F14601622A630E@dnce02.ent.ti.com> 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> <4E243F49.9020706@redhat.com> In-Reply-To: <4E243F49.9020706@redhat.com> Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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/msg00052.txt.bz2 Hi, In fact there was a more detailed mail on testsuite on the 1st of April 201= 1 where I did not get answer (maybe people throught it was a joke due to th= e date ;-) ). That is fairly understandable so I was about to follow-up but= I moved from Linaro to unexpectingly long customer assignment and team was= also too busy to help The goal we have now is to move to v1.5 and clean all that (already tested = fine by some other guy in the team). As Franck suggested, issues shall be t= ranscribed to bugzilla and we can take care of that. And I also still have to follow-up on remarks about power management relate= d topics but that's another story ! Regards Fred Frederic Turgis OMAP Platform Business Unit - OMAP System Engineering - Platform Enablement > Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet= . 036 420 040 R.C.S Antibes. Capital de EUR 753.920 -----Original Message----- > From: William Cohen [mailto:wcohen@redhat.com] > Sent: Monday, July 18, 2011 4:12 PM > To: Turgis, Frederic > Cc: Da Zheng; systemtap@sourceware.org > Subject: Re: error to run systemtap in an ARM platform > > 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 >