This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: About Call-pending-DSRs
- To: windy <windy_yuan at 263 dot net>
- Subject: Re: [ECOS] About Call-pending-DSRs
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Thu, 29 Mar 2001 17:13:55 +0100
- Cc: "ecos-discuss at sourceware dot cygnus dot com" <ecos-discuss at sourceware dot cygnus dot com>,Gary Thomas <gthomas at redhat dot com>, Mark Salter <msalter at redhat dot com>
- Organization: Red Hat UK Ltd.
- References: <200103290310.TAA20885@cygnus.com>
windy wrote:
>
> Referring to eCos Interrupt Model in eCos document , it allow irq recur when call DSR.
> But in ARM implement code(vector.s), I found the irq haven't be re-enable immediately
> after calling isr handle. if enable MACRO CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK,
> ECOS will enable irq and call dsr continue,if we haven't enable this MACRO,ecos will call
> dsr directly without enabling irq.
> What if I enable irq directly after calling isr handle?
Then you can keep on getting more interrupts, and those will mount up on
the thread stack.
But admittedly this seems unavoidable if not using a separate interrupt
stack, so it may indicate a bug that it doesn't enable interrupts anyway.
Gary? Mark?
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine