public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: "Turgis, Frederic" <f-turgis@ti.com>
Cc: Da Zheng <zhengda1936@gmail.com>,
	       "systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: Re: error to run systemtap in an ARM platform
Date: Mon, 18 Jul 2011 14:13:00 -0000	[thread overview]
Message-ID: <4E243F49.9020706@redhat.com> (raw)
In-Reply-To: <13872098A06B02418CF379A158C0F1460162204601@dnce02.ent.ti.com>

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

  reply	other threads:[~2011-07-18 14:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  0:58 Da Zheng
2011-07-15  9:43 ` Mark Wielaard
2011-07-15 20:00   ` Da Zheng
2011-07-15 20:15     ` Frank Ch. Eigler
     [not found]       ` <4E20A714.9020404@gmail.com>
2011-07-15 20:50         ` Frank Ch. Eigler
2011-07-15 20:46     ` William Cohen
2011-07-15 21:29       ` Da Zheng
2011-07-16  0:23         ` Turgis, Frederic
2011-07-18 14:13           ` William Cohen [this message]
2011-07-18 19:02             ` Da Zheng
2011-07-18 20:10               ` William Cohen
2011-07-18 20:18                 ` William Cohen
2011-07-18 20:41                 ` Da Zheng
2011-07-23 22:56                   ` Zheng Da
2011-07-24  1:57                     ` Frank Ch. Eigler
2011-07-24 16:10                       ` Frank Ch. Eigler
2011-07-25 10:04                     ` Mark Wielaard
2011-07-25 19:34                       ` Da Zheng
2011-07-25 15:46                     ` William Cohen
2011-07-25 19:36                       ` Da Zheng
2011-07-25 20:46                         ` Mark Wielaard
2011-07-25 17:17                     ` William Cohen
2011-07-25 19:56                       ` Da Zheng
2011-07-26 14:03                         ` William Cohen
2011-07-26 17:47                           ` Da Zheng
2011-07-19 11:38             ` Turgis, Frederic
2011-07-18 14:00         ` William Cohen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E243F49.9020706@redhat.com \
    --to=wcohen@redhat.com \
    --cc=f-turgis@ti.com \
    --cc=systemtap@sourceware.org \
    --cc=zhengda1936@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).