[PATCH 07/16] posix: Make POSIX API aware of scheduler instances
Gedare Bloom
gedare at rtems.org
Mon Jun 20 15:45:31 UTC 2016
>> diff --git a/cpukit/posix/src/mutexgetprioceiling.c b/cpukit/posix/src/mutexgetprioceiling.c
>> index 2df4776..eda02cb 100644
>> --- a/cpukit/posix/src/mutexgetprioceiling.c
>> +++ b/cpukit/posix/src/mutexgetprioceiling.c
>> @@ -46,6 +46,7 @@ int pthread_mutex_getprioceiling(
>> _POSIX_Mutex_Acquire_critical( the_mutex, &queue_context );
>>
>> *prioceiling = _POSIX_Priority_From_core(
>> + &_Scheduler_Table[ 0 ],
> Why not _Scheduler_Get_own(executing)? Does it matter which scheduler
> control is used.
>
>
>> @@ -56,13 +52,26 @@ int pthread_mutex_setprioceiling(
>> the_mutex = _POSIX_Mutex_Get_no_protection( mutex );
>> _Assert( the_mutex != NULL );
>>
>> + scheduler = &_Scheduler_Table[ 0 ];
>> +
> ditto.
>
> -Gedare
Nevermind, I see it is dealt with later by the map function.
More information about the devel
mailing list