From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [Xenomai-help] Interrupt shield From: Philippe Gerum In-Reply-To: References: Content-Type: text/plain Date: Thu, 16 Nov 2006 22:32:34 +0100 Message-Id: <1163712755.4980.16.camel@domain.hid> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: rpm@xenomai.org List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sebastian Smolorz Cc: xenomai@xenomai.org 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.