This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
cyg_scheduler_read_lock() seems wrong in the synthetic environment
- From: Dan Jakubiec <djakubiec at yahoo dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Mon, 8 Dec 2003 12:11:32 -0800 (PST)
- Subject: [ECOS] cyg_scheduler_read_lock() seems wrong in the synthetic environment
We are running eCos on an ARM7 platform and shadowing this development
in a Linux synthetic environment. I noticed that in the synthetic
environment the scheduler lock count seems to be "off-by-one". When
running in "thread context", cyg_scheduler_read_lock() always reports 1
(instead of 0) and DSR report >= 2. The lock count never drops below
1.
On our real ARM hardware, the lock counts look right: 0 for thread
context, >= 1 for DSRs. However, both environments seem to be working
fine.
Is this expected behavior or is something wrong? Can someone explain
what is/should be going on here?
Thanks,
--
Dan Jakubiec
Systech Corp
__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.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