From: Jan Kiszka <jan.kiszka@domain.hid>
To: jean-olivier.villemure@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] My work on Xenomai integration to LTTng / LTTV
Date: Tue, 31 Oct 2006 18:34:12 +0100 [thread overview]
Message-ID: <45478914.4030309@domain.hid> (raw)
In-Reply-To: <1162302832.3687.12.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]
Jean-Olivier Villemure wrote:
> 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.
Wow, great news!
>
> 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?
- CPU usage (see /proc/xenomai/stat for average numbers, but we should
now be able to precisely calculate them for a specific period)
- Waiting times after activation (maybe one can define deadlines later
and verify them)
- Number of preemptions per second or whatever while a task is runnable
- Number of blockades a task faces due to unavailable resources
(mutexes, semaphores, etc.)
...just to through some first ideas in.
>
> 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!
So you have an integrated I-pipe+LTTng patch which is able to record
events under any context and push them to Linux non-RT user-space,
right? How does this work, what impact does it have (also compared to
the I-pipe tracer, which is not light-weight)? And, most important, when
will we be able to see some code (ipipe add-on patch)? Would be good to
assess how this could be integrated on the long term into
I-pipe/Xenomai, at least until required LTTng parts become mainstream.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2006-10-31 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 13:53 [Xenomai-core] My work on Xenomai integration to LTTng / LTTV Jean-Olivier Villemure
2006-10-31 17:34 ` Jan Kiszka [this message]
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=45478914.4030309@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=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.