From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Makarand Pradhan <makarandpradhan@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Need help with ipipe trace
Date: Thu, 01 Mar 2012 20:38:37 +0100 [thread overview]
Message-ID: <4F4FD03D.8070502@domain.hid> (raw)
In-Reply-To: <4F4FCC10.4000501@domain.hid>
On 03/01/2012 08:20 PM, Makarand Pradhan wrote:
> Hi,
>
> I am trying to get an ipipe trace and need help to get it working.
>
> I am using Xenomai 2.6 with linux 3.0.0.
>
> The kernel is compiled with following config parameters:
>
> CONFIG_IPIPE_DEBUG=y
> CONFIG_IPIPE_DEBUG_CONTEXT=y
> CONFIG_IPIPE_DEBUG_INTERNAL=y
> CONFIG_IPIPE_TRACE=y
> CONFIG_IPIPE_TRACE_ENABLE=y
> CONFIG_IPIPE_TRACE_MCOUNT=y
> CONFIG_IPIPE_TRACE_IRQSOFF=y
> CONFIG_IPIPE_TRACE_SHIFT=14
> CONFIG_IPIPE_TRACE_VMALLOC=y
> CONFIG_IPIPE_TRACE_PANIC=y
> CONFIG_DEBUG_KERNEL=y
>
> The /proc/ipipe direcotry is created.
>
> In my application I am using:
>
> xntrace_max_begin(0); -> To start tracing.
> xntrace_max_end(0); -> To stop tracing.
>
> The function trace that I get in the /proc/ipipe/trace/max file does not
> have the xenomai calls that I am invoking e.g. rt_timer_read.
The I-pipe tracer is a kernel-space tracer, so, you will only get the
trace for the services which emit a system call. So, when calling
rt_timer_read, you should see __rt_timer_read in the trace.
You can find all the documentation we have about the I-pipe tracer here:
http://www.xenomai.org/index.php/I-pipe:Tracer
--
Gilles.
next prev parent reply other threads:[~2012-03-01 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 19:20 [Xenomai-help] Need help with ipipe trace Makarand Pradhan
2012-03-01 19:38 ` Gilles Chanteperdrix [this message]
2012-03-01 20:02 ` Makarand Pradhan
2012-03-01 20:28 ` Gilles Chanteperdrix
2012-03-01 20:57 ` Makarand Pradhan
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=4F4FD03D.8070502@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=makarandpradhan@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.