Got it. Thank you for the clarification.
On Fri, Mar 26, 2021 at 8:32 PM Gedare Bloom wrote:
> On Thu, Mar 25, 2021 at 11:30 PM Richi Dubey wrote:
> >
> > Thanks for your quick response!
> >
> >> Each scheduler has its own lock. There are a couple of more locks
> involved.
> >
> > I understand.
On Thu, Mar 25, 2021 at 11:30 PM Richi Dubey wrote:
>
> Thanks for your quick response!
>
>> Each scheduler has its own lock. There are a couple of more locks involved.
>
> I understand.
>
> I backtracked a little and found that we have:
> _Thread_State_acquire_critical( the_thread, lock_context )
Thanks for your quick response!
Each scheduler has its own lock. There are a couple of more locks involved.
I understand.
I backtracked a little and found that we have:
_Thread_State_acquire_critical( the_thread, lock_context );
to lock access to thread-specific variables.
_Scheduler_Acquire_c
On 24/03/2021 08:07, Richi Dubey wrote:
How does RTEMS handle cases where two different cores access
scheduler-related functions at the same time?
Each scheduler has its own lock. There are a couple of more locks involved.
For ex., Can they access (or modify) the Scheduler_strong_APA_Context
