f7843e2198
we can use g_cpu_lockset to determine whether we are currently in the scheduling lock, and all accesses and modifications to g_cpu_lockset, g_cpu_irqlock, g_cpu_irqset are in the critical section, so we can directly operate on it. test: We can use qemu for testing. compiling make distclean -j20; ./tools/configure.sh -l qemu-armv8a:nsh_smp ;make -j20 running qemu-system-aarch64 -cpu cortex-a53 -smp 4 -nographic -machine virt,virtualization=on,gic-version=3 -net none -chardev stdio,id=con,mux=on -serial chardev:con -mon chardev=con,mode=readline -kernel ./nuttx Signed-off-by: hujun5 <hujun5@xiaomi.com> |
||
---|---|---|
.. | ||
CMakeLists.txt | ||
Make.defs | ||
sem_clockwait.c | ||
sem_destroy.c | ||
sem_holder.c | ||
sem_initialize.c | ||
sem_post.c | ||
sem_recover.c | ||
sem_reset.c | ||
sem_rw.c | ||
sem_setprotocol.c | ||
sem_tickwait.c | ||
sem_timedwait.c | ||
sem_timeout.c | ||
sem_trywait.c | ||
sem_wait.c | ||
sem_waitirq.c | ||
semaphore.h | ||
spinlock.c |