This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 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.

Although if there are multiple DSRs to be run, you don't know what order they will be run in. This could matter if some DSRs take a long time to run, like the serial driver one (unfortuately).


Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
>>>>> Visit us in booth 2527 at the Embedded Systems Conference 2004 <<<<<
March 30 - April 1, San Francisco http://www.esconline.com/electronicaUSA/
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]