Error by make export by extensa ESP32

2023-04-06 Thread Roberto Bucher
Hi I've finally reached to generate code for ESP32 using pysimCoder. My board is a OLIMEX ESP32-POE board, Starting from the esp32-devkitc:wifinsh configuration we set CONFIG_ARCH_CHIP_ESP32WROOM32=y and the generation of the nuttx code is ok. The problems start when I do a "make export":

Re: [Breaking change] Move nxmutex to sched

2023-04-06 Thread Gregory Nutt
On 4/6/2023 9:09 AM, Petro Karashchenko wrote: Also pthread_mutex is a solution for user space, but would be good to have something similar for kernel space. During adding nxmutex wrapper to the code many misuse issues were identified, so it is adding safety during coding and does not allow mis

Re: [Breaking change] Move nxmutex to sched

2023-04-06 Thread Gregory Nutt
On 4/6/2023 9:03 AM, Petro Karashchenko wrote: Yes. The main "mutex" attribute differentiating it from a binary semaphore is that it can be released only by a holder thread (even if priority inheritance is not enabled). And that is for the basic mutex, but recursive mutex also allows nested "ob

Re: [Breaking change] Move nxmutex to sched

2023-04-06 Thread Tomek CEDRO
On Thu, Apr 6, 2023 at 2:58 PM Gregory Nutt wrote: > > Oh my God! That sounds terrible! Does this change actually do > /anything /positive. > > Duplicating the internal implementation of Linux is /NOT /positive. It > is irrelevant. > > Adopting GNU/Linux interfaces as a functional specification

Re: [Breaking change] Move nxmutex to sched

2023-04-06 Thread Petro Karashchenko
I agree with Greg! If we can have stable operation of priority inheritance with semaphores then we can build mutex as a macro based wrapper (mostly as it is now). One thing that I can think of is adding a "mutex" attribute to a semaphore and creating a separate task list for faster scheduling, bu

Re: [Breaking change] Move nxmutex to sched

2023-04-06 Thread Gregory Nutt
Oh my God!  That sounds terrible!  Does this change actually do /anything /positive. Duplicating the internal implementation of Linux is /NOT /positive.  It is irrelevant. Adopting GNU/Linux interfaces as a functional specification made since.  But duplicating the ibnternal implementation of

Re: [Breaking change] Move nxmutex to sched

2023-04-06 Thread zyfeier
Hi, All: The main purpose of this PR is to separate mutex and semaphore and to improve the performance of mutex. Regarding the issues mentioned in the email , here is a summary: 1. The number of system calls will increase. After separating mutex and semaphore, futex support will be added in th