This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Will unlock_inner() be called twice during Real Time Clock Interrupt in ecos?
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: <jameshq at liverpool dot ac dot uk>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: 24 Sep 2002 23:51:36 +0100
- Subject: Re: [ECOS] Will unlock_inner() be called twice during Real Time Clock Interrupt in ecos?
- References: <200209242054.g8OKsGN04326@webmail1.liv.ac.uk>
<jameshq@liverpool.ac.uk> writes:
> Thanks you very much for pointing out my mistake.
> Are the followings correct (after correcting my mistake)?
> Thanks
>
> Q1.
> Does that mean: In the Real Time Clock tick interrupt ,The
> unlock_inner() will **not** run in
> Cyg_RealTimeClock::dsr()-->tick()-->unlock(). unlock_inner() will just
> **only** called before calling to the Cyg_RealTimeClock::dsr(), and
> when return from the Cyg_RealTimeClock::dsr() thread context switching
> will happens on the old thread's stack.
Exactly.
>
>
> Q2.
> Does all DSR() run on the interrupt stack if a serperate interrupt
> stack is in used?
>
Yes.
--
Nick Garnett - eCos Kernel Architect
http://www.eCosCentric.com/
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss