| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Delete unused POSIX_Message_queue_Control::process_shared.
|
|
|
|
|
| |
Make _POSIX_Message_queue_Create_support() static since it is only used
by mq_open().
|
|
|
|
| |
Update #2555.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Ensure that kernel and user space system call protoypes are identical.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
There is no need for an ISR lock since the Dual_ported_memory_Control is
immutable after initialization. ISR disable is enough for deletion
safety on uni-processor configurations.
Update #2555.
|
|
|
|
| |
Update #2555.
|
|
|
|
|
|
| |
Use _Thread_queue_Flush_critical() to atomically release the barrier.
Update #2555.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This simplifies the code since the object location is no longer used.
Remove superfluous header includes.
|
|
|
|
|
|
|
| |
Avoid Giant lock for CORE mutex and semaphore flush and delete
operations.
Update #2555.
|
|
|
|
| |
Update #2555.
|
|
|
|
|
|
|
|
| |
Rename _CORE_RWLock_Obtain_for_reading() into
_CORE_RWLock_Seize_for_reading(). Rename
_CORE_RWLock_Obtain_for_writing() into _CORE_RWLock_Seize_for_writing().
Rename _CORE_RWLock_Release() into _CORE_RWLock_Surrender(). This
avoids confusion with the ISR lock acquire and release.
|
|
|
|
|
|
| |
Rename _CORE_barrier_Wait() into _CORE_barrier_Seize(). Rename
_CORE_barrier_Release() into _CORE_barrier_Surrender(). This avoids
confusion with the ISR lock acquire and release.
|
|
|
|
|
|
| |
Rename _MRSP_Obtain() into _MRSP_Seize(). Rename _MRSP_Release() into
_MRSP_Surrender(). This avoids confusion with the ISR lock acquire and
release.
|
|
|
|
|
| |
Make the id the first parameter since usual callers get the object
identifier as the first parameter themself.
|
|
|
|
|
| |
Make the id the first parameter since usual callers get the object
identifier as the first parameter themself.
|
|
|
|
| |
Remove unused location parameter.
|
|
|
|
|
|
| |
Remove unused supports_global parameter. Convert
_Objects_Initialize_information() to a macro to avoid use of
RTEMS_MULTIPROCESSING define for each caller.
|
|
|
|
|
|
|
|
| |
Replace _Thread_queue_Flush() with _Thread_queue_Flush_critical() and
add a filter function for customization of the thread queue flush
operation.
Update #2555.
|
|
|
|
|
|
|
| |
Delete _POSIX_Mutex_Get(). Use _POSIX_Mutex_Get_interrupt_disable()
instead.
Update #2555.
|
|
|
|
| |
Add and use _CORE_mutex_Release().
|
|
|
|
| |
Remove superfluous location parameter.
|
|
|
|
|
| |
Simplify _POSIX_Condition_variables_Wait_support(), since there is no
need to validate the mutex twice.
|
|
|
|
| |
Parameter was unused.
|
|
|
|
|
| |
This prevents use of the object after the flush on uni-processor
configurations.
|
|
|
|
|
|
|
| |
Use proper CORE_semaphore_Status for _CORE_semaphore_Flush() and
_CORE_semaphore_Destroy() operations.
Close #2696.
|
|
|
|
|
| |
This prevents use of the object after the flush on uni-processor
configurations.
|
| |
|
|
|
|
|
|
|
| |
Drop status parameter since each caller used
CORE_MESSAGE_QUEUE_STATUS_WAS_DELETED.
Remove superfluous _CORE_message_queue_Flush().
|
|
|
|
|
| |
Remove superfluous _CORE_message_queue_Flush() since we completely
re-initialize the structure in _CORE_message_queue_Initialize().
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Add a lock and use a chain iterator for safe iteration during concurrent
user extension addition and removal.
Ensure that dynamically added thread delete and fatal extensions are
called in reverse order.
Update #2555.
Update #2692.
|
|
|
|
| |
Simplify _User_extensions_Handler_initialization().
|
|
|
|
|
|
| |
Extension create and delete is protected by the object allocator lock.
Update #2555.
|
|
|
|
|
| |
Add a chain iterator for safe iteration of chains with concurrent node
extraction.
|
|
|
|
|
|
|
| |
This service was marked as deprecated long prior to the 4.11 release
series and is now being removed.
closes #2676.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This is the very simple implementation specified by the Open Group
for implementations with 1:1 kernel thread to user thread mappings.
http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_getconcurrency.html
updates #2680.
|
|
|
|
|
|
|
|
|
|
| |
POSIX key destructors must be called during thread restart. Just like
the POSIX cleanup handlers. This ensures that the TLS object
destructors are called during thread restart for example. It is
important for the global construction, which uses a thread restart to
run the Init task in a clean environment.
Close #2689.
|
|
|
|
|
|
| |
rcsid is defined, but not used. So discard it.
Signed-off-by: Peng Fan <van.freenix@gmail.com>
|