From: Philippe Gerum <rpm@xenomai.org>
To: xenoka09@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] T_WARNSW ignored?
Date: Sat, 15 Aug 2009 16:10:54 +0200 [thread overview]
Message-ID: <1250345454.2933.91.camel@domain.hid> (raw)
In-Reply-To: <alpine.DEB.2.00.0908151512440.7626@domain.hid>
On Sat, 2009-08-15 at 15:14 +0200, Waschk,Kolja wrote:
> Hi,
>
> well my guess was correct, the quickly increasing MSW without SIGXCPU was just
> due to a forced mode switch with rt_task_set_mode... how silly, sorry for
> bothering!
No problem. I'm rather concerned by the fact that
rt_task_set_mode(...T_PRIMARY...) is still being used for the wrong
purpose, but this bug is mine originally. The point is that there should
be no valid reason to switch modes explicitly in any user level code,
Xenomai knows better in any case, and only does it internally when
required.
Explicit switching is currently required by a few skin libraries for
internal purpose, I should have exported some hidden syscall to provide
this anti-feature, instead of crippling the rt_task_set_mode() interface
with the wacky T_PRIMARY mode bit. Anyway...
The xnshadow_relax() issue on Blackfin led to use it the wrong way as a
workaround; please report this kind of bug before applying any
workaround, so that a proper fix could be found in parallel. TIA,
>
> Kolja
>
>
--
Philippe.
prev parent reply other threads:[~2009-08-15 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 9:05 [Xenomai-help] T_WARNSW ignored? Kolja Waschk
2009-08-14 10:05 ` Gilles Chanteperdrix
2009-08-14 10:08 ` Kolja Waschk
2009-08-14 10:13 ` Philippe Gerum
2009-08-14 10:26 ` Kolja Waschk
2009-08-14 15:05 ` Philippe Gerum
2009-08-14 19:52 ` Waschk,Kolja
2009-08-15 14:01 ` Philippe Gerum
2009-08-15 13:14 ` Waschk,Kolja
2009-08-15 14:10 ` Philippe Gerum [this message]
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=1250345454.2933.91.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=xenoka09@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.