All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michael Haberler <mail17@mah.priv.at>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] i-pipe tracer on in production kernels? (was Re: Altera Cyclone V)
Date: Sat, 11 Jan 2014 19:11:54 +0100	[thread overview]
Message-ID: <52D1896A.8070202@xenomai.org> (raw)
In-Reply-To: <3FA64D57-1BB1-4B4A-AB25-AC8E280105F8@mah.priv.at>

On 01/11/2014 11:22 AM, Michael Haberler wrote:
> 
> http://www.xenomai.org/index.php/I-pipe:Tracer describes the trace
> API, which could be useful to track down issues
> 
> Q: does enabling the tracer incur significant overhead if compiled in
> but unused, or is it reasonable to leave it on in a production
> kernel?
> 
> if the former, we might have to build/make available a second i-pipe
> tracer enabled kernel to track down issues 'in the field'; if the
> latter, it'd be less build/distribution chores

Normally, with DYNAMIC_FTRACE, there should be a way to reduce the
overhead. Unfortunately, the I-pipe tracer disables DYNAMIC_FTRACE,
because at some point in the past, it did not work (with the I-pipe
tracer) on ARM. We could re-enable DYNAMIC_FTRACE and try and understand
why it does not work (if it still does not work), but that means you
would have to add patches on top of the I-pipe patch, because all I-pipe
patches released for some time, forbid DYNAMIC_FTRACE with the I-pipe
tracer, at least on ARM.

-- 
                                                                Gilles.


  parent reply	other threads:[~2014-01-11 18:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 19:52 [Xenomai] Altera Cyclone V Lowell Gilbert
2014-01-07 20:25 ` Gilles Chanteperdrix
2014-01-08 22:45   ` Lowell Gilbert
2014-01-08 23:19     ` Gilles Chanteperdrix
2014-01-09 18:06       ` Lowell Gilbert
2014-01-10  0:14         ` Gilles Chanteperdrix
2014-01-14  0:15       ` Lowell Gilbert
2014-01-07 22:19 ` Charles Steinkuehler
2014-01-07 22:47   ` Gilles Chanteperdrix
2014-01-07 22:55     ` Charles Steinkuehler
2014-01-07 23:13       ` Gilles Chanteperdrix
2014-01-08  0:51         ` Charles Steinkuehler
2014-01-08  4:04           ` Charles Steinkuehler
2014-01-08  8:21             ` Gilles Chanteperdrix
2014-01-08  8:58             ` Gilles Chanteperdrix
2014-01-11 10:22           ` [Xenomai] i-pipe tracer on in production kernels? (was Re: Altera Cyclone V) Michael Haberler
2014-01-11 12:16             ` Gilles Chanteperdrix
2014-01-11 18:11             ` Gilles Chanteperdrix [this message]
2014-01-11 18:20             ` Philippe Gerum
2014-01-11 18:27               ` Gilles Chanteperdrix
2014-01-11 19:01                 ` Philippe Gerum
2014-01-11 19:11                   ` Gilles Chanteperdrix
2014-01-08  3:21     ` [Xenomai] Altera Cyclone V Lowell Gilbert

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=52D1896A.8070202@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=mail17@mah.priv.at \
    --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.