[lttng-dev] LTTng / Android questions
Karim Yaghmour
karim.yaghmour at opersys.com
Sun Aug 12 16:08:59 EDT 2012
Hi Mathieu,
Apologies for the delayed response, I was in Bangalore for a few weeks
with limited bandwidth (time-wise.)
I haven't had the chance to try getting LTTng 2.0 to work on Android.
The most up-to-date pointer I would've had was the Ericsson work which
was pointed to in a later email in this thread. I remain, however,
interested in any work in this direction, please keep me posted.
Thanks,
--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour
On 12-08-02 05:52 PM, Mathieu Desnoyers wrote:
> Hi Karim,
>
> Any word of advice about building LTTng 2.0 on Android ? See the
> question below.
>
> Thanks,
>
> Mathieu
>
> * Glossop, Kent (kent.glossop at intel.com) wrote:
>> Thanks.
>>
>> I've been trying to understand how to do the lttng cross build for
>> Android. Is there a particular approach that you would expect people
>> to most naturally use (e.g. if I were to write up a "how-to")?
>> It seems like one approach is to use a full Android build area, adding
>> the lttng components to the "external" directory, requiring Android.mk
>> files. If the files aren't generated automatically, this adds
>> maintenance. (There is a tool called androgenizer that can be used
>> assist, but that seems undesirable to include for a "general"
>> solution.) Another approach would be to build some of components with
>> options to configure, in conjunction with an Android build (or NDK?)
>> area. Would you view one of these (or something else), a "preferred"
>> way?
>>
>> Thanks,
>> Kent
>>
>> -----Original Message-----
>> From: Mathieu Desnoyers [mailto:mathieu.desnoyers at efficios.com]
>> Sent: Tuesday, July 24, 2012 2:21 PM
>> To: Glossop, Kent
>> Cc: christian.babeux at efficios.com
>> Subject: Re: LTTng / Android questions
>>
>> Hi Kent,
>>
>> It should work, theoretically. Testing would be welcome. We did port of the lttng tools (except for the kernel tracer) to NetBSD/FreeBSD recently, where we had to circumvent lack of TLS support, so this requirement on the glibc is now gone from the 2.0 lttng series.
>>
>> If Android kernel is close enough to mainline, lttng-modules should work too.
>>
>> I'm CCing christian, who is currently looking at the embedded aspect of the continuous integration heterogenous cluster we are currently building.
>>
>> Thanks,
>>
>> Mathieu
>>
>>
>> * Glossop, Kent (kent.glossop at intel.com) wrote:
>>> Mathieu,
>>>
>>> I'm interested in LTTng for Android. If you have time, a few
>>> questions... (Let me know if this would be better posted to
>>> lttng-dev.)
>>>
>>> From what I can tell from previous postings to lttng-dev and other places:
>>>
>>> - People apparently used a previous version with a 2.x kernel with some changes and building it in
>>>
>>> - There was/is an issue with glibc vs. bionic for lttng's use of shared memory
>>>
>>> - Back in Feb. there was a demo done of LTTng on Android done using a copy of glibc
>>>
>>> - There are at least some changes being made that mention Android (e.g. a TLS change that mentioned Android about 2 months ago)
>>>
>>> What I'm interested in:
>>>
>>> - Are there directions somewhere for building LTTng for use with Android? (e.g. how to configure component and reference an Android build area rather than things for the native host?)
>>>
>>> - How much is expected to work on Android?
>>>
>>> - Is glibc still needed?
>>>
>>> - Are there people actively working on Android support (if it doesn't already work)?
>>>
>>> - Do you have a rough idea what might be involved for an Android x86 version beyond arm?
>>>
>>> Ideally, I would like to be able to install a minimal set of pieces, preferably on to a stock phone, collect LTTng traces, and use the viewer on linux (or maybe even windows if linux-tools works there.) Then, to do that with x86 Android in addition to arm...
>>>
>>> Thanks,
>>> Kent Glossop, Intel
>>>
>>
>> --
>> Mathieu Desnoyers
>> Operating System Efficiency R&D Consultant EfficiOS Inc.
>> http://www.efficios.com
>
More information about the lttng-dev
mailing list