From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>,
Jan Kiszka <jan.kiszka@domain.hid>,
xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] yet another test tool
Date: Wed, 22 Mar 2006 22:57:54 +0100 [thread overview]
Message-ID: <17441.51298.263977.458028@domain.hid> (raw)
In-Reply-To: <17440.14775.987528.126782@domain.hid>
Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > The current implementation is one thing (we could fix it), the purpose
> > of the tool is another, and actually, this is the latter which seems
> > useful to me. By sharing some common tests between native preemption and
> > real-time sub-systems like Xeno, we would make performance comparisons
> > more relevant.
>
> Ok. I added the tool. I also had to add some cruft to configure.in to
> get the --wrap flags in src/testsuite/cyclic/Makefile.
>
> Now, running this test seem to have uncovered a bug with the binary heap
> based timers that the latency test did not show. I am investigating on
> this, but in the mean time, please do not enable the binary heap timers
> option.
The bug was not due to the binary heap timers list, but to the fact that
the POSIX skin module (and other skins modules) did call
xnpod_stop_timer.
I removed all such calls of xnpod_stop_timer, since xnpod_shutdown calls
xnpod_stop_timer when needed (that is, only when shutting down the last
skin pod).
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2006-03-22 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 22:18 [Xenomai-core] yet another test tool Jan Kiszka
2006-03-20 8:20 ` Philippe Gerum
2006-03-20 15:21 ` Gilles Chanteperdrix
2006-03-20 16:36 ` Jan Kiszka
2006-03-20 19:10 ` Gilles Chanteperdrix
2006-03-20 21:13 ` Philippe Gerum
2006-03-21 17:36 ` Gilles Chanteperdrix
2006-03-22 21:57 ` Gilles Chanteperdrix [this message]
2006-03-20 17:20 ` Philippe Gerum
2006-03-20 17:36 ` Jan Kiszka
2006-03-20 17:50 ` 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=17441.51298.263977.458028@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=rpm@xenomai.org \
--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.