This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: regarding hal_interrupt_stack_call_pending_DSRs call
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: Brij Bihari Pandey <fuzzhead012 at yahoo dot com>
- Cc: eCos-discuss <ecos-discuss at sources dot redhat dot com>
- Date: 14 Oct 2002 18:37:50 +0100
- Subject: Re: [ECOS] regarding hal_interrupt_stack_call_pending_DSRs call
- References: <20021014102340.92525.qmail@web21007.mail.yahoo.com>
Brij Bihari Pandey <fuzzhead012@yahoo.com> writes:
> I checked out the sources and it seems to me that the
> hal_interrupt_stack_call_pending_DSRs is called only
> via unlock_inner call. Am I right in this? Or there
> are other places via which this function can be
> called?
It can only be called via unlock_inner().
>
> Can I also infer from the comment mentioned in file,
> that there can never be a situation that results in
> nested calls for this function (A-> hal...DSRs -> ....
> -> XYZ -> hal...DSRs).
This can never happen because DSRs are only called when the scheduler
lock is about to go zero. This would not be true of any nested calls.
>
> Otherwise jumping to interrupt stack without looking
> will be catastrophic.
>
Of course. Please give me credit for having actually thought about
this and having written the code to not contain such elementary
errors.
--
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