This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: clock interrupt fails to call unlock_inner()
- From: Satish Kumar <satish at bvt dot sc dot sanyo dot co dot jp>
- To: Satish Kumar <satish at bvt dot sc dot sanyo dot co dot jp>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Tue, 23 Sep 2003 17:21:37 +0900
- Subject: Re: [ECOS] clock interrupt fails to call unlock_inner()
- References: <20030923161857.3B4E.SATISH@bvt.sc.sanyo.co.jp>
i think the sched_lock identifier is not initialized..i see some
definitioins in smp.hxx
saty
On Tue, 23 Sep 2003 16:42:25 +0900
Satish Kumar <satish@bvt.sc.sanyo.co.jp> wrote:
> Hi,
> when the clock interrupt takes place, my
> hal_interrupt_stack_call_pending DSRs func is not called. following is
> the intermediate path when an clock interupt takes place.
> i.e
> when i enter into the interrupt_end() func, following steps are
> followed:
> Set_Save_Context()--|
> post_DSR()
> Set_Save_Context()--|
> |
> Get_Current_Thread()----|
> | Set_Save_Context()
> |
> Get_Sched_lock()
> |
> unlock()(fails to call unlock_inner() func)
> |----
> |
> Set_Sched_lock()...!!!!!
> |
> |-----
> unlock()
> Get_Current_Thread()----|
> |
> Set_Save_Context()
>
>
> Now the problem is that when the unlock() func is stepped in the
> identifier "__lock" is undefined and hence Set_Sched_lock()
> is called..instead of unlock_inner() func which is responsible for
> invoking hal_interrupt_stack_call_pending_DSRs.
>
> this fails to call the DSRs from RealTimeClock and hence i fail to test
> any of my program which is dependent on the clock interrupt.
>
> well my dsr_list contains the data entry for the clock interrupt
> generated and also the interrupt vector no: are all correct.
>
>
> so, is there somethin which i m failin to understand.
>
> thanks
> satish
>
>
>
> --
> Satish Kumar <satish@bvt.sc.sanyo.co.jp>
>
>
> --
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
--
Satish Kumar <satish@bvt.sc.sanyo.co.jp>
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss