sched/pthread: repalce sched_lock to enter_critical_section

[Gary-Hobson]

Summary

Repalce sched_lock to enter_critical_section

After RR is enabled, an interrupt occurs during this period and the task cannot be switched

Impact

Testing

[pkarashchenko]

I'm in the middle of implementation for ostest for scheduler lock/unlock and has draft change to fix it #7464
Could you please try if the change helps in this particular case?

UPDATE: No, the changes are still not ready

[pkarashchenko]

Please see apache/nuttx-apps#1711

[Gary-Hobson]

I'm in the middle of implementation for ostest for scheduler lock/unlock and has draft change to fix it #7464 Could you please try if the change helps in this particular case?

UPDATE: No, the changes are still not ready

This change has nothing to do with priority inheritance.
It is encountered when running the libuv test set, and there is a case (uv_run_test async) that will busy wait for a mutex.

The time to turn off scheduling in pthread_mutex_timedlock is too long. After turning on the time slice rotation, every time an interrupt is triggered, it is in the state of off scheduling, resulting in the task not being able to switch tasks.

[pkarashchenko]

Please fix commit message sched_lcok -> sched_lock

[Gary-Hobson]

Please fix commit message sched_lcok -> sched_lock
done

[pkarashchenko]

Please rebase to get CI pass

[pkarashchenko]

Can issue be easily reproduced? What are the steps?

[xiaoxiang781216]

@Gary-Hobson please rebase your change.