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: <bob dot koninckx at o-3s dot com>, <ecos-discuss at sources dot redhat dot com>
- Date: Tue, 27 Jul 2004 08:15:27 +0200
- Subject: AW: [ECOS] Blocking restricted in DSRs
> Things like waiting for a semaphore. Blocking is something you do at
> thread level. The thread "blocks" (or goes to sleep) until another
> thread or interrupt wakes it up again. Basically, this waking
> up is done
> by the scheduler, which explains why you should not block in a DSR,
> which is called _before_ the scheduler.
>
> Hope this makes it a little bit clearer,
>
> Bob
Ok, the docu says sending signals to condition variables is ok from a DSR. But AFAIK this has always be done together with locking the associated mutex first... from the DSR then. But the docu also says using cyg_mutex_lock() should be used only from thread context, not from DSR. So, what's the right way then ?
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