[lttng-dev] supporting new processor
Yannick Brosseau
yannick.brosseau at gmail.com
Mon Apr 22 11:41:24 EDT 2013
For the kernel module, from what I've seen, you'll be missing the
syscall tracing, but the rest of the tracepoints should work.
Syscall tracing requires some architecture specific code in the kernel
itself.
On 2013-04-22 10:17, Jérémie Galarneau wrote:
> Hi,
>
> Generally speaking, URCU is the most architecture-specific library of
> the project and it does support MIPS. Once it is compiled and
> installed, you should be able to build lttng-ust, lttng-tools and the
> kernel modules.
>
> I'd recommend running each project's test suite since I don't think
> that architecture has been thoroughly tested. Let us know if you
> encounter any problem on your particular architecture.
>
> Regards,
> Jérémie
>
> On Mon, Apr 22, 2013 at 1:30 AM, Madhusudan Bhat <madhu.b77 at gmail.com> wrote:
>> Hi All,
>>
>> I need to support lttng tools, I have new MIPS based multi core processor on
>> which 3.7 linux kernel boots up.
>>
>> To support lttng tools, does it require any drivers/kernel hook ups to new
>> processor? Or is it independent of processor architecture?
>>
>> For ex, to support Oprofile tools, we need to provide oprofile driver which
>> is specific to particular processor. In similar ways,any thing is required
>> to support lttng tools?
>>
>> thanks,
>> Madhu.
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev at lists.lttng.org
>> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>
>
>
More information about the lttng-dev
mailing list