All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Philippe Gerum <rpm@xenomai.org>, Michael Haberler <haberlerm@gmail.com>
Cc: xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Q: LTTNG & xenomai status
Date: Mon, 30 Mar 2015 18:11:48 +0200	[thread overview]
Message-ID: <551975C4.8050501@web.de> (raw)
In-Reply-To: <55191E4E.9020803@xenomai.org>

On 2015-03-30 11:58, Philippe Gerum wrote:
> On 03/30/2015 11:51 AM, Michael Haberler wrote:
>>
>>
>> 2015-03-30 11:17 GMT+02:00 Philippe Gerum <rpm@xenomai.org
>> <mailto:rpm@xenomai.org>>:
>>
>>     On 03/30/2015 10:58 AM, Michael Haberler wrote:
>>     > 2015-03-26 23:37 GMT+01:00 Michael Haberler <haberlerm@gmail.com <mailto: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.
>>
>>
>> given that there is no code pertaining to LTTng in xenomai-2.6, I assume
>> you consider this the responsibility of the LTTng maintainers?
>>
>> I will inquire on the lttng-dev list, but does "usual" imply they
>> usually take care of this?
>>  
> 
> No, this implies that people have to take care of this when they need
> it. By "usual", I mean "each time I had to do this".
> 

We used to integrate Xenomai with LTTng back then but gave up as LTTng
made no progress towards upstream and the efforts became too high. These
days you get Xenomai kernel instrumentation via ftrace, at least in 3.0.
Maybe give that a try first and then tell us what is missing.

For 2.6, we have some out-of-tree ftrace patches for x86-64 as well. Can
refresh our queue [1] if needed.

Jan

[1] http://git.xenomai.org/xenomai-jki.git/log/?h=queues/ftrace

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20150330/ad27fa32/attachment.sig>

  reply	other threads:[~2015-03-30 16:11 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
2015-03-30  9:51     ` Michael Haberler
2015-03-30  9:58       ` Philippe Gerum
2015-03-30 16:11         ` Jan Kiszka [this message]
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=551975C4.8050501@web.de \
    --to=jan.kiszka@web.de \
    --cc=haberlerm@gmail.com \
    --cc=rpm@xenomai.org \
    --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.