From: gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
To: Lars Segerlund <lars.segerlund@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Newbie question about profiling.
Date: Thu, 23 Sep 2010 22:45:05 +0530 [thread overview]
Message-ID: <4C9B8B19.5050205@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTi=6NUEod+pFZPhyZL0v8C-v1iMvQDZnuKgWxj9E@mail.gmail.com>
On Thursday 23 September 2010 08:12 PM, Lars Segerlund wrote:
> Hello,
>
> I am fairly new to RT Preempt, but now to realtime embedded systems.
> I am trying to get EMC2 running on RT Preempt, and I was given some
> old patches on the mailing list which miracously worked.
>
> From here I am trying to get a complete system built from scratch
> with 'latest' RT Preempt and EMC2.
>
> My question is how to go about finding out what causes latencies and
> jitter, I have no problem to create some code to benchmark latencies
> or jitter, but how do I find out where the kernel is spending it's
> time ?
>
>
Hi,
You can start with RT functional testcases which are already available
in LTP (https://rt.wiki.kernel.org/index.php/LTP%28Realtime_Test_Tree%29)
If you find tests failing for some reason, then it can be good place to
start
investigating with the help of kernel inbuilt tracing tool (ftrace) where
you have options to trace particular subsystem (irqoff, preemptoff,
wakeup..)
Check kernel Documentation/trace/ftrace.txt.
Thanks,
Gowrishankar
> Any hints would be much appreciated, since i really don't have a clue
> on how to go about this.
>
> I was thinking that if I could create a realtime task to test for a
> specific thing, I really would like a log of what the kernal was doing
> right before this.
> The only way I can think of is creating a module with a ring buffer (
> spill over ), and tracing the scheduler or interrupt handler .... ( by
> hackíng some code to specifically do this ), this would only add a
> small overhead AFAIK.
>
> Any idea's anyone ? or hints ?
>
> It seem's like just the thing that already might have a solution in
> place, so I figured I should not reinvent the wheel.
>
> / best regards, Lars Segerlund.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-09-23 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 14:42 Newbie question about profiling Lars Segerlund
2010-09-23 14:58 ` Pradyumna Sampath
2010-09-23 17:15 ` gowrishankar [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=4C9B8B19.5050205@linux.vnet.ibm.com \
--to=gowrishankar.m@linux.vnet.ibm.com \
--cc=lars.segerlund@gmail.com \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).