linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pradyumna Sampath <pradysam@gmail.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 16:58:52 +0200	[thread overview]
Message-ID: <AANLkTi=mXtZHFdkJsMNEd6rzkTW1UXt_7SpXNH+=YO6s@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=6NUEod+pFZPhyZL0v8C-v1iMvQDZnuKgWxj9E@mail.gmail.com>

Hi Lars,

On Thu, Sep 23, 2010 at 4:42 PM, Lars Segerlund
<lars.segerlund@gmail.com> wrote:

>  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.

Yeah in the last couple of years a lot of tools have been developed to
do exaclty this kind of thing. You could look for ..

- FTrace https://rt.wiki.kernel.org/index.php/Ftrace
- Tuna
- LTTng
..

Im sure there are a couple more but Ive used ftrace and LTTng and they
are pretty cool.

best regards
/prady

-- 
http://www.prady.in
--
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

  reply	other threads:[~2010-09-23 14:58 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 [this message]
2010-09-23 17:15 ` gowrishankar

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='AANLkTi=mXtZHFdkJsMNEd6rzkTW1UXt_7SpXNH+=YO6s@mail.gmail.com' \
    --to=pradysam@gmail.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).