From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org, "Moser, Dan" <DMoser@domain.hid>
Subject: Re: FW: [Xenomai-help] Xenomai thread runtime statistics
Date: Fri, 17 Mar 2006 17:13:59 +0100 [thread overview]
Message-ID: <441AE047.6020505@domain.hid> (raw)
In-Reply-To: <441ADFAA.9040602@domain.hid>
Jan Kiszka wrote:
> Philippe Gerum wrote:
>
>>Moser, Dan wrote:
>>
>>>Hi,
>>>
>>>I am still searching for ways (hopefully via some API(s)) to get Xenomai
>>>run-time thread execution info (my original post is below).
>>>
>>>Being a newbie, I apologize if the answer "should be obvious". I am
>>>still getting up to speed with both Linux and Xenomai.
>>>
>>>Is there a better list on which I should post this question?
>>>
>>
>>This question is perfectly relevant to this list, the thing is that
>>there's no simple, built-in way of getting execution stats for real-time
>>threads yet. The best way to find out the execution time of your work
>>cycle would be to measure it using the high precision clock information.
>
>
> Hmm, wouldn't it be feasible to add such statistics to I-pipe level? I'm
> thinking of something like time spent in domain X, Y, Z vs. the overall
> runtime, preferably converted to percentage usage.
>
This would be nice, but only part of the issue, since you might have several
real-time context switches occurring in a single Xenomai domain activation.
> Jan
>
--
Philippe.
next prev parent reply other threads:[~2006-03-17 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 15:17 FW: [Xenomai-help] Xenomai thread runtime statistics Moser, Dan
2006-03-17 15:57 ` Philippe Gerum
2006-03-17 16:11 ` Jan Kiszka
2006-03-17 16:13 ` Philippe Gerum [this message]
2006-03-17 16:22 ` Jan Kiszka
2006-03-17 16:26 ` 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=441AE047.6020505@domain.hid \
--to=rpm@xenomai.org \
--cc=DMoser@domain.hid \
--cc=jan.kiszka@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.