All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Michael Haberler <haberlerm@gmail.com>, xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Q: LTTNG & xenomai status
Date: Mon, 30 Mar 2015 11:17:16 +0200	[thread overview]
Message-ID: <5519149C.4030505@xenomai.org> (raw)
In-Reply-To: <CADvZd9af58_fHQYDMpQ+g3caew0_W144kCKGeCpFi7uGP3FD1A@mail.gmail.com>

On 03/30/2015 10:58 AM, Michael Haberler wrote:
> 2015-03-26 23:37 GMT+01:00 Michael Haberler <haberlerm@gmail.com>:
> 
>> what is the status on using LTTNG tracepoints in an RT thread? the last
>> discussion has been a while back, like 2010ish
>>
>> LTTNG 2.5.1 is in the debian jessie stream. Can I use that as-is?
>>
>> Any special precautions I need to take, or do the stock instructions for
>> LTTNG apply?
>>
> 
> noting that CONFIG_FTRACE was disabled for performance reasons:
> http://www.xenomai.org/pipermail/xenomai/2013-January/027272.html
> 
> that would suggest *functionally* it is not an issue, and LTTng layers
> ontop of CONFIG_FTRACE for kernel tracing
> 
> or am I overlooking something?
> 

Functionally it is not an issue, but the LTT core for any given LTT
version might not be entirely safe for running over a kernel with
pipelined interrupts. Fixing this is part of the usual process of
merging LTTng and the I-pipe.

-- 
Philippe.


  reply	other threads:[~2015-03-30  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 22:37 [Xenomai] Q: LTTNG & xenomai status Michael Haberler
2015-03-30  8:58 ` Michael Haberler
2015-03-30  9:17   ` Philippe Gerum [this message]
2015-03-30  9:51     ` Michael Haberler
2015-03-30  9:58       ` Philippe Gerum
2015-03-30 16:11         ` Jan Kiszka
2015-03-31  0:00           ` Michael Haberler

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=5519149C.4030505@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=haberlerm@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.