All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: ROSSIER Daniel <Daniel.Rossier@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: LTTng intergration roadmap
Date: Thu, 18 May 2006 10:13:08 +0200	[thread overview]
Message-ID: <446C2C94.70908@domain.hid> (raw)
In-Reply-To: <FDBBB5CC70676540B3EF7CFE83FD94E04A4528@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 3643 bytes --]

ROSSIER Daniel wrote:
> Hi Jan,
> 
> Sorry for my late answer.
> 
>> -----Message d'origine-----
>> De : jan.kiszka@domain.hid [mailto:jan.kiszka@domain.hid]
>> Envoyé : lundi, 15. mai 2006 17:18
>> À : xenomai-core
>> Cc : Alexis Berlemont; ROSSIER Daniel
>> Objet : LTTng intergration roadmap
>>
>> Hi,
>>
>> the need for a high-level tracing tool constantly increases with the
>> growing code base of Xenomai applications.
>>
>> Yesterday I started a short discussion with Alexis about the status of
>> his LTTng combo patch, the Xenomai integration, and the advances of
>> LTTng itself. But there are certainly more people interested in this
>> topic and may contribute ideas, comments, or even concrete code.
>>
>> Daniel, you once said that some of your students would start to work on
>> this topic. In which domain precisely, more at patch level or rather on
>> tools? What is the scheduled beginning and/or deadline for this thesis?
>>
> 
> Yes, it's right; my student is actually working on a first investigation in order to prepare its diploma project which starts from October to December.
> So, the most insteresting results should not come up until then. 
> 
> The project consists in enhancing LTTng with Xenomai events and some specific algorithmic filtering on the related events, such as detecting abnormal situations (deadline misses, priority inversion at a certain level, etc.); the way how events are presented are also an issue to be considered (events per threads and not per process, different ways to represent the events). We are therefore very open to some proposals and ideas.
> The interesting thing is that Jean-Olivier (the student) will perform his project at Matthieu Denoyers's premises at Montreal; besides, he already visited him to have first discussions. I think this will help us greatly.

That's indeed a very thrilling chance to exchange our needs with the
ideas and plans of the LTTng community!

> 
>> Moreover, does anyone on this list recently tried LTTng on standard
>> Linux? Can we consider it reasonably stable and usable? One new thing
>> about LTTng internals which Alexis brought up were changes in the custom
>> tracing event interface. As this is a rather crucial point with respect
>> to the Xenomai instrumentation, we certainly do not want to change it
>> back and forth until LTTng stabilises.
>>
>> Jan
> 
> Thanks also to Alexis. The way how to generated lttng events matches with how we're doing now; we will also examine his Xenomai events and give you a feedback.
> 
> Of course, we keep the forum informed about the progress, but as mentioned before, it risks to evolve quite slowly on our side since the "big" project is for the three last months.

Ok, as I see this we need a clear roadmap for the time until
Jean-Olivier starts his main work, and it would be good to coordinate
his major topics ahead-of-time to avoid duplicate work. I think we
should soon have some basic LTTng support for Xenomai on one or two
major archs which should allow to track task and domain switches. This
would already be very helpful for analysing deadline misses or
application lock-ups, and it is my wish for the near future.

I do not know all features and potential limitations of LTTng in details
but I guess there will still be more than enough room for improvements
by Jean-Olivier. Do you already have concrete ideas for his work? E.g.
improved instrumentation, better filtering, specific arch support, or
extension to the front-end tools? The clearer his plans are, the better
we can coordinate other activities.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  parent reply	other threads:[~2006-05-18  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17  6:45 [Xenomai-core] RE: LTTng intergration roadmap ROSSIER Daniel
2006-05-17  7:12 ` Romain Lenglet
2006-05-18  8:13 ` Jan Kiszka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-15 15:18 [Xenomai-core] " Jan Kiszka
2006-05-15 20:40 ` [Xenomai-core] " Alexis Berlemont
2006-05-16 12:25   ` Jan Kiszka

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=446C2C94.70908@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=Daniel.Rossier@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.