From: Philippe Gerum <rpm@xenomai.org>
To: Sebastian Smolorz <ssm@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Interrupt shield
Date: Thu, 16 Nov 2006 22:32:34 +0100 [thread overview]
Message-ID: <1163712755.4980.16.camel@domain.hid> (raw)
In-Reply-To: <E1Gke0B-0003BT-CA@mailer.emlix.com>
On Thu, 2006-11-16 at 10:57 +0100, Sebastian Smolorz wrote:
> Hello,
>
> can anybody confirm this behaviour? If I configure the I-shield into the
> kernel and start the latency test the RT tasks have not activated T_SHIELD
> although the documentation states it (and btw in rt_task_create this bit is
> set).
The documentation of rt_task_create() is wrong. The default behaviour
should be to create tasks with disabled I-shield support.
> If I try to set T_SHIELD inside the display task, the system hangs, a
> soft lockup appears and sometimes a few correct lines of the display task are
> printed, followed by the next lockup.
Confirmed here (on x86).
>
> Explainable?
>
Yes. I must have screwed up something somewhere, many moons ago.
> I'm testing on ARM with my S3C24xx I-pipe patch.
>
The I-shield does not depend on any arch-specific code; it's purely
based on a few generic Adeos services making use of the pipeline
abstraction. Will fix.
> --
> Sebastian
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
next prev parent reply other threads:[~2006-11-16 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 9:57 [Xenomai-help] Interrupt shield Sebastian Smolorz
2006-11-16 15:50 ` Jan Kiszka
2006-11-16 16:03 ` Sebastian Smolorz
2006-11-16 21:32 ` Philippe Gerum [this message]
2006-11-17 11:21 ` Philippe Gerum
2006-11-20 9:24 ` Sebastian Smolorz
-- strict thread matches above, loose matches on Subject: below --
2005-12-15 8:02 [Xenomai-help] Interrupt Shield smannori
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=1163712755.4980.16.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=ssm@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.