All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Jan Kiszka <jan.kiszka@domain.hid>, xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] yet another test tool
Date: Mon, 20 Mar 2006 22:13:41 +0100	[thread overview]
Message-ID: <441F1B05.1090505@domain.hid> (raw)
In-Reply-To: <17438.65058.166546.339686@domain.hid>

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>  > As a first step, I would vote for establishing that generic service to
>  > redirect the userspace return path to some arbitrary handler in hard-RT
>  > context. Then we can think about how to handle signal injection from
>  > Linux vs. injection from Xenomai gracefully.
> 
> Ok, the first idea was a bad idea. Will try the second, or the
> alternative proposed by Philippe.
> 
>  > 
>  > > 
>  > >  > 
>  > >  > What do you think, is it worth including as a POSIX counterpart for
>  > >  > testsuite/latency?
>  > > 
>  > > There are a few details that I do not like about this tool, but we may
>  > > take it, and fix the details later.
>  > 
>  > It's a real hack, isn't it ;)? But what precisely do you mean?
> 
> What I dislike most, is the lack of return values check. This may work
> well with Linux, but not with Xenomai. I would also prefer a clean
> shutdown using pthread_cancel, after all sigwait and *nanosleep are
> cancellation points, so it should work even without resorting to cleanup
> handlers.
> 

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. Additionally, I'm convinced that the POSIX skin is an 
underutilized goodie albeit it works damn well and obviously favours a 
close integration within the Linux environment, simply because there is 
a lack of explanation about it. Illustrating how one could leverage it 
is always a good thing.

-- 

Philippe.


  reply	other threads:[~2006-03-20 21:13 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 [this message]
2006-03-21 17:36         ` Gilles Chanteperdrix
2006-03-22 21:57           ` Gilles Chanteperdrix
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=441F1B05.1090505@domain.hid \
    --to=rpm@xenomai.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.