From: matthew.khouzam@ericsson.com (Matthew Khouzam)
Subject: [ltt-dev] LTTng and RTAI
Date: Fri, 4 Feb 2011 13:59:59 -0500 [thread overview]
Message-ID: <4D4C4CAF.1010303@ericsson.com> (raw)
In-Reply-To: <20110204115413.vr2a7frjyxc8sooo@secure.et-inf.fho-emden.de>
That would be interesting to try out.
One issue with RTAI (at least that I've experienced) is that is is
supported generally by older kernels. RTAI itself is at 3.8+ I think, so
your kernel is probably something around 2.6.17?
From the compatibility matrix
(http://git.lttng.org/?p=lttv.git;a=blob_plain;f=doc/developer/lttng-lttv-compatibility.html;hb=HEAD)
I would suggest trying the 0.6.2, the trace version would be 0.7, You
would need LTTV version 0.8.62, TMF would not work for visualizing this.
At home I have RTAI 3.8 and an instrumented kernel works fine on it. I
tried tracing something and it doesn't affect the latency that much. (On
an athlon 64 3000+ my max latency passes from 40 us to 42-43
empirically) I did not read the trace output, but the files were created
and there were no big error messages.
I tried it during some RT apps and the apps worked properly, BUT I had a
hard rt system that was requiring rtai but had latency requirements in
the 500us range.
If your max latency is 50 us and your deadline is 50.01 us, you will
have issues.
For tl;dr It should work with the right version. Works for me, try it out.
On 11-02-04 05:54 AM, babrah at et-inf.fho-emden.de wrote:
> Hi,
>
> I am wondering if LTTng is usable with RTAI 3.4. Do you know anything
> about it?
>
> kind regards,
>
> Bernd Abraham
>
>
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
prev parent reply other threads:[~2011-02-04 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 10:54 babrah
2011-02-04 18:59 ` Matthew Khouzam [this message]
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=4D4C4CAF.1010303@ericsson.com \
--to=matthew.khouzam@ericsson.com \
/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