All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: David <david35k@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] filter ipipe tracing
Date: Tue, 14 Jan 2014 13:47:32 +0100	[thread overview]
Message-ID: <52D531E4.4040407@xenomai.org> (raw)
In-Reply-To: <CA+6vZpS6Mw7rfvHnNBkB-9Jd9C-UUjRJ_hD6Ket_f__8F8iaLg@mail.gmail.com>

On 01/14/2014 01:35 PM, David wrote:
> Dear,
>
> I'm actually tracing my Xenomai drivers/syscalls thanks to the ipipe trace
> facility. Actually, every "ipipe/xenomai/rtdm drivers" procedures are
> traced. I give a try with 5000 points, I'm able to trace about 5ms of
> execution. This is already a huge help for some problems but (a) it is too
> short for my new needs. The performance impact of tracing appears big
> (about x2 on performance ?), (b) it makes my application instable (100% of
> CPU usage).
>
> (a) Is it possible to trace about 1-10s of execution ? (any hint ?).
> (b) Could we reduce performance impact for tracing ? I used FTRACE in the
> past, it was possible to filter the events or procedure names traced but I
> don't know how to proceed with ipipe tracing.

If you are only interested in the events you generate, then you can 
disable tracing of function entries and exit, and generate the events 
you are interested in with ipipe_trace_special.


-- 
					    Gilles.


  reply	other threads:[~2014-01-14 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 12:35 [Xenomai] filter ipipe tracing David
2014-01-14 12:47 ` Gilles Chanteperdrix [this message]
2014-01-14 17:30   ` David
2014-01-14 18:04     ` Jan Kiszka

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=52D531E4.4040407@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=david35k@gmail.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.