From: "Stéphane ancelot" <sancelot@numalliance.com>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] ipipe tracer question
Date: Thu, 03 Nov 2016 16:29:08 +0100 [thread overview]
Message-ID: <581B57C4.8020609@numalliance.com> (raw)
In-Reply-To: <20161103093605.2228191c@md1em3qc>
On 03/11/2016 09:36, Henning Schild wrote:
> Am Wed, 2 Nov 2016 18:10:48 +0100
> schrieb Stéphane ancelot<sancelot@numalliance.com>:
>
>
>> Hi,
>> I have got an RT task that seems being disturbed by some system
>> driver.
>>
>> So, I have setted up ipipe tracer in kernel.
>>
> The tracing uses the kernel tracing infrastructure. Use the
> sysfs-Interface or a tool like trace-cmd or perf to collect traces.
> https://www.kernel.org/doc/Documentation/trace/ftrace.txt
>
>
I am now able to trace in the kernel.
I made some function trace in the shell, but I have not managed to find
where is my problem.
I want to find where my tasks spend more time than usuallly. e.g. (end
task - start task) > 500us
I have some references to cobalt_head_sysentry , cobalt_head_sys
I made a trace with trace-cmd and I am able to load it with kernelshark.
a bit difficult to understand the graph.
>> But I do not know where to go now ?
>> I suppose being on the right way, but what to do next ?
>>
>> Regards,
>> S.Ancelot
>>
>>
>> _______________________________________________
>> Xenomai mailing list
>> Xenomai@xenomai.org
>> https://xenomai.org/mailman/listinfo/xenomai
>>
next prev parent reply other threads:[~2016-11-03 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 17:10 [Xenomai] ipipe tracer question Stéphane ancelot
2016-11-03 8:36 ` Henning Schild
2016-11-03 15:29 ` Stéphane ancelot [this message]
2016-11-03 16:38 ` Henning Schild
2016-11-04 15:46 ` Stéphane ancelot
2016-11-04 15:59 ` Henning Schild
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=581B57C4.8020609@numalliance.com \
--to=sancelot@numalliance.com \
--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.