On 18/03/16 19:04, Dario Faggioli wrote:
> as doing that include changing the scheduler lock
> mapping for the pCPU itself, and the correct way
> of doing that is:
> - take the lock that the pCPU is using right now
>(which may be the lock of another scheduler);
> - change the mapping of the l
as doing that include changing the scheduler lock
mapping for the pCPU itself, and the correct way
of doing that is:
- take the lock that the pCPU is using right now
(which may be the lock of another scheduler);
- change the mapping of the lock to the RTDS one;
- release the lock (the one tha
On Fri, Mar 18, 2016 at 3:04 PM, Dario Faggioli
wrote:
> as doing that include changing the scheduler lock
> mapping for the pCPU itself, and the correct way
> of doing that is:
> - take the lock that the pCPU is using right now
>(which may be the lock of another scheduler);
> - change the m
