Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTng on OMAP3 with Android
Date: Sat, 19 Jun 2010 12:15:48 -0400	[thread overview]
Message-ID: <20100619161548.GG22882@Krystal> (raw)
In-Reply-To: <4C04DA1F.3050105@ti.com>

* Hugo Dupras-XID (h-dupras at ti.com) wrote:
>
> Hello,
>
> I try to apply and use LTTng on OMAP3 with Android. I applied LTTng  
> 0.124 kernel patches to the Android kernel because Android is always at  
> 2.6.29 kernel version.
> LTTng seems to work correctly, I obtain data and viewing them with LTTV.  
> Unfortunately the timings are just wrong and some tasks appears smaller  
> than they should be. I saw a correction for the OMAP trace clock with  
> the 0.134 kernel patches, but i blocked applying these patches to the  
> android kernel (some files dont exit in the 2.6.29 kernel).
>
> So my question is : Is there anybody who succeed to apply LTTng on  
> Android, and how ??

Have you looked at the lttng-omap tree ? It is based on 2.6.32-rc8-omap
though.

See http://lttng.org/content/download

LTTng OMAP support prior to this one won't support suspend/resume and
DVFS correctly. The LTTng version you have for 2.6.29 is possibly based
on the "generic" timestamp support, which provides a 1 HZ accuracy,
which is pretty coarse.

Hope this helps,

Mathieu

>
> Thanks advance,
>
> Regards,
> Hugo
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com




           reply	other threads:[~2010-06-19 16:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4C04DA1F.3050105@ti.com>]

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=20100619161548.GG22882@Krystal \
    --to=compudj@krystal.dyndns.org \
    /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