This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
AW: Blocking restricted in DSRs
- From: "Neundorf, Alexander" <Alexander dot Neundorf at jenoptik dot com>
- To: "Nick Garnett" <nickg at ecoscentric dot com>, <ecos-discuss at sources dot redhat dot com>
- Date: Tue, 27 Jul 2004 18:28:33 +0200
- Subject: AW: [ECOS] Blocking restricted in DSRs
...
> Threads can call blocking functions with the scheduler locked. The
> lock is essentially a per-thread variable so when the thread is
> resumed the lock is returned to its former value.
IOW cyg_scheduler_lock() ensures that the scheduler doesn't run as long as the thread which called cyg_scheduler_lock() doesn't call a synchronization function which calls itself the scheduler, right ?
But still I don't understand the code.
cyg_scheduler_lock() calls Cyg_Scheduler::lock() in sched.inl, which calls inc_sched_lock(). This I find in smp.hxx. I don't see any thread specific data there, so how can this act thread-specific ?
Thanks
Alex
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss