On Thu, Oct 13, 2005 at 02:42:58PM +0200, Stefan Sommerfeld wrote:
Hi,
I working with latest eCos on a XScale system and i noticed a very high
delay between the ISR and the corresponding after some time. The system
is
not idle and does a lot of things (including multiple threads and
irq's). I
see a delay between ISR and DSR over 30 ms.
I checked the system's DSR, to make sure there's no DSR which runs very
long and i looked for possible cyg_scheduler_lock() calls. What i wonder
about is, i see that sometimes a quick cyg_scheduler_lock() happen which
between the long ISR/DSR delay. So it looks like scheduling is active
and
running but the DSR is not called.
What could influence the ISR to DSR delay besides scheduler_lock and
still
active DSR? I thought a DSR will be called as soon as possible. Could
this
be a wrong eCos kernel setup?
DSRs are only allowed to run with it is safe to run a DSR. This in
fact means that when the schedular is locked DSRs cannot run. Once the
schedular is unlocked the DSR will get to run.
So the schedular is probably locked when the ISR happens and you see a
delay. When the ISR exits the DSR does not get to run. When you see a
cyg_scheduler_lock() this will actually be a nested lock inside
another lock. So the DSR will only get to run when both locks are
unlocked. This might actually be telling you something. A double lock
suggests something more complex is going on. It might be worth seeing
if a single lock gives you an acceptable delay but a double lock is
unacceptable. If so you can then just find the double lock case and
simply the code. Otherwise you need to investigate all locks and find
onces which are taking too long.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss