From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] User Space tracing on ARM 2.6.23
Date: Tue, 4 Aug 2009 09:37:03 -0400 [thread overview]
Message-ID: <20090804133703.GC23807@Krystal> (raw)
In-Reply-To: <305625.28501.qm@web63201.mail.re1.yahoo.com>
* Ajit R (ajitrzid at yahoo.com) wrote:
>
> Hi
> My config is the following:
> Architecture: ARM11 MPCORE Uniprocessor
> Lttv version: 0.10.0-pre1
> LTTng version: 0.10.0-pre5
> LTT Control: 0.45
> kernel version: 2.6.23.1
>
> applied the userspace patches. Compilation errors in "ltt-syscall.c"
>
> ltt_reserve_slot(trace, channel, &transport_data, reserve_size, &slot_size, &tsc)
>
> has to be:
>
> ltt_reserve_slot(trace, channel, &transport_data, reserve_size, &slot_size, &tsc,cpu);
>
> and
>
> trace->ops->user_errors(trace, index, data_size, &dbg);
> which has to be
> trace->ops->user_errors(trace, index, data_size, &dbg,cpu);
>
> Added this to get cpu after preempt_disable() -->
>
> cpu = smp_processor_id();
>
>
> I can see sys_ltt_trace and sys_register_markers in "/proc/kallsyms" after compilation.
>
> From: ltt-syscall.c
> /*
> * TODO: ONLY permit userspace markers to write in userspace channels.
> */
> asmlinkage long sys_register_markers(const struct user_markers *begin,
> const struct user_markers *end)
> {
> }
>
>
>
> Seems like register_markers does nothing with the system call.
> Are there any examples on howto use the older userspace tracing anywhere: register_markers and ltt_trace ?
>
Given you use old LTTng versions, you will have to dig into the versions
implemented in newer versions yourself.
Sorry, there is only a limited set of versions I can focus on.
Mathieu
> Thanks
> Ajit
>
>
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
prev parent reply other threads:[~2009-08-04 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 13:22 Ajit R
2009-08-04 13:37 ` Mathieu Desnoyers [this message]
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=20090804133703.GC23807@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