Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Change all references of rtems.com to rtems.org. | Chris Johns | 2014-03-21 | 1 | -1/+1 |
| | |||||
* | score: Add SMP lock profiling support | Sebastian Huber | 2014-03-14 | 1 | -5/+11 |
| | |||||
* | score: Add function to destroy SMP locks | Sebastian Huber | 2014-03-11 | 1 | -0/+16 |
| | |||||
* | score: Add local context to SMP lock API | Sebastian Huber | 2014-03-11 | 1 | -42/+68 |
| | | | | | | | | | | | Add a local context structure to the SMP lock API for acquire and release pairs. This context can be used to store the ISR level and profiling information. It may be later used to enable more sophisticated lock algorithms, e.g. MCS locks. There is only one lock that cannot be used with a local context. This is the per-CPU lock since here we would have to transfer the local context through a context switch which is very complicated. | ||||
* | score: ISR lock API changes | Sebastian Huber | 2013-08-01 | 1 | -6/+50 |
| | |||||
* | score: Add and use ISR locks | Sebastian Huber | 2013-07-31 | 1 | -0/+141 |
ISR locks are low-level locks to protect critical sections accessed by threads and interrupt service routines. On single processor configurations the ISR locks degrade to simple ISR disable/enable sequences. No additional storage or objects are required. This synchronization primitive is supported on SMP configurations. Here SMP locks are used. |