[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
rtems_semaphore_obtain problems identified
- Date: Wed, 02 May 2007 08:41:47 -0500
- From: joel.sherrill at oarcorp.com (Joel Sherrill)
- Subject: rtems_semaphore_obtain problems identified
Chris Johns wrote:
> Johan Zandin wrote:
>> * RTEMS bug 1237 exists in all RTEMS versions and probably
>> on most platforms. It is related to interrupts occuring
>> during task switches and the symptoms are that stacks
>> may grow too large, overwriting other memory areas.
> I have looked over the patch and it only references the sparc cpu. I am
> confused about the reference to "most platforms" reference. Do you mean just
> sparc platforms ?
This particular scenario was that a near continuous stream of high rate
could result in barely getting back to the interrupted task and getting
and preempting from that task again and again without ever clearing off
interrupt stack frames.
This scenario is completely possible on other CPUs but is aggravated by
interrupt stack frame on the SPARC. I suspect that design factors in
code that are port specific may avoid this problem on some ports.
I'm not saying it couldn't happen on another architecture just that each
port has to
be evaluated on its own merits. Some ports run _ISR_Dispatch at the ISR
level of the interrupt that generated the preempt so there would be a
on how many ISR Dispatches could stack.
The SPARC runs ISR Dispatch with all interrupts enabled so the previous ISR
is fair gain to occur again.
> rtems-users mailing list
> rtems-users at rtems.com