Re: [ECOS] interrupt and scheduling

["Stefano Martini" <martini at sci dot univr dot it>]

I apologize you.

Please drag my previous message into the trash.
I have made a mistake in my simple program.
Nick is right.


----- Original Message ----- 
From: Stefano Martini 
To: ecos-discuss@sources.redhat.com 
Sent: Thursday, March 04, 2004 12:28 PM
Subject: Re: [ECOS] interrupt and scheduling


Nick Garnett wrote:
> Martini Stefano <martini@sci.univr.it> writes:
>>
>>Is the RealTimeclock::dsr called immediately after
>>the RealTimeclock::isr or is it scheduled by the
>>scheduler?
> 
> 
> If the interrupt occurs while the current thread has the scheduler
> locked then the DSR is deferred (hence the name) until the thread
> unlocks the scheduler. If the scheduler is not locked, then the DSR
> will be run immediately as part of the exit from the interrupt.

Thank you Nick for your replay.
Now, I have made a simple program in which the first instruction
is a cyg_scheduler_lock(). No cyg_sheduler_unlock() is present
in the program.

Into the RealTimeClock::dsr I have a diag_printf to see if this
method is called.
When I start the program, I see the messages printed by the diag_printf.
If the scheduler is locked, why is the dsr executed?

Thanks in advance
Stefano



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss