Gregory Nutt 360539afac Priority inheritance: When CONFIG_SEM_PREALLOCHOLDERS==0, there is only a single, hard-allocated holder structure. This is problem because in sem_wait() the holder is released, but needs to remain in the holder container until sem_restorebaseprio() is called. The call to sem_restorebaseprio() must be one of the last things the sem_wait() does because it can cause the task to be suspended. If in sem_wait(), a new task gets the semaphore count then it will fail to allocate the holder and will not participate in priority inheritance. This fix is to add two hard-allocated holders in the sem_t structure: One of the old holder and one for the new holder.		2017-03-10 09:30:15 -06:00
..
Make.defs	sem_setprotocol: Handle a case of missing proxy for sem_setprotocol. Reorder so that (1) this error is avoided, and (2) >No proxy is needed if priority inheritance is not enabled.	2016-11-03 18:51:38 -06:00
sem_destroy.c	Remove some empty file section section header comments	2016-02-17 17:38:39 -06:00
sem_holder.c	Priority inheritance: When CONFIG_SEM_PREALLOCHOLDERS==0, there is only a single, hard-allocated holder structure. This is problem because in sem_wait() the holder is released, but needs to remain in the holder container until sem_restorebaseprio() is called. The call to sem_restorebaseprio() must be one of the last things the sem_wait() does because it can cause the task to be suspended. If in sem_wait(), a new task gets the semaphore count then it will fail to allocate the holder and will not participate in priority inheritance. This fix is to add two hard-allocated holders in the sem_t structure: One of the old holder and one for the new holder.	2017-03-10 09:30:15 -06:00
sem_initialize.c	sem_tickwait(): Add a new, non-standard function to perform timed semaphore waits. It is functionally equialent to the standard sem_timedwait(), but more efficient for use in higher performance device drivers. Requested by Max Neklyudov	2015-08-01 07:31:09 -06:00
sem_post.c	Add some comments.	2016-11-05 09:44:29 -06:00
sem_recover.c	nuttx/sched: Replace irqsave() with enter_critical_section(); replace irqrestore() with leave_critical_section()	2016-02-14 08:17:46 -06:00
sem_reset.c	Update some comments	2016-03-06 13:50:26 -06:00
sem_setprotocol.c	Missing # on endif	2016-11-03 21:27:52 -06:00
sem_tickwait.c	nuttx/sched: Replace irqsave() with enter_critical_section(); replace irqrestore() with leave_critical_section()	2016-02-14 08:17:46 -06:00
sem_timedwait.c	Move cancellation point definitions to their own header file.	2016-12-10 09:08:26 -06:00
sem_timeout.c	nuttx/sched: Replace irqsave() with enter_critical_section(); replace irqrestore() with leave_critical_section()	2016-02-14 08:17:46 -06:00
sem_trywait.c	sem_wait() and sem_trywait() no longer modify the errno value UNLESS an error occurs. This allows these functions to be used internallly without clobbering the errno value.	2016-11-09 07:01:49 -06:00
sem_wait.c	Cancellation points: Fix some backward logic in conditional compilation.	2017-02-02 06:42:41 -06:00
sem_waitirq.c	nuttx/sched: Replace irqsave() with enter_critical_section(); replace irqrestore() with leave_critical_section()	2016-02-14 08:17:46 -06:00
semaphore.h	Within the OS, when a thread obtains a semaphore count it must call sem_addholder() if CONFIG_PRIORITY_INHERITANCE is enabled. If a count is available, then sem_wait() calls sem_addholder(), otherwise it waited for the semaphore and called sem_addholder() when it eventually received the count.	2016-10-26 07:23:15 -06:00
spinlock.c	SMP: There were certain conditions that we must avoid by preventing releasing the pending tasks while withn a critical section. But this logic was incomplete; there was no logic to prevent other CPUs from adding new, running tasks while on CPU is in a critical section.	2016-12-27 08:49:07 -06:00