From: Jean-Olivier Villemure <jean-olivier.villemure@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-core] My work on Xenomai integration to LTTng / LTTV
Date: Tue, 31 Oct 2006 08:53:51 -0500 [thread overview]
Message-ID: <1162302832.3687.12.camel@domain.hid> (raw)
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Hello,
I'm currently working on the integration of Xenomai tracing in LTTng
(Linux Trace Toolkit Next Generation) and the event viewing in LTTV
(Linux Trace Toolkit Viewer).
At this moment, I 'm tracing events about task handling, period and
soon, mutex and semaphore synchronization.
Inserting traqcing points in Xenomai nucleus is not very difficult, my
main work is focus on the controlflow viewer module of LTTV. At this
moment, we can open a trace and view:
- Task state : init, started, running, suspended, overrunning (period
miss)
- Period timer tick for periodic task
- Textual information about the task (name, period, priority, birth)
- Mutex/semaphore owned by specific task
- Soon task waiting on mutex/semaphore
Look at the screenshot to have a better idea.
The next step will be to generate some statistics, for this step I will
need your help. As Xenomai users, which kind of stats would you want to
compute?
After that, I'll study the possibilities of simulating an execution
trace from an existing trace by modifying some parameters (period
length, ...)
Any ideas are welcome!
Jean-Olivier Villemure
[-- Attachment #2: Type: image/png, Size: 121459 bytes --]
[-- Attachment #3: Type: image/png, Size: 1209 bytes --]
[-- Attachment #4: Type: image/png, Size: 66360 bytes --]
next reply other threads:[~2006-10-31 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 13:53 Jean-Olivier Villemure [this message]
2006-10-31 17:34 ` [Xenomai-core] My work on Xenomai integration to LTTng / LTTV Jan Kiszka
2006-11-01 6:07 ` Philippe Gerum
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=1162302832.3687.12.camel@domain.hid \
--to=jean-olivier.villemure@domain.hid \
--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.