f6a9e91057
Only in the non-critical region, nuttx can the respond to the irq and not hold the lock When returning from the irq, there is no need to check whether the lock needs to be restored 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> |
||
---|---|---|
.. | ||
Kconfig | ||
Make.defs | ||
sparc_v8_copystate.c | ||
sparc_v8_doirq.c | ||
sparc_v8_initialstate.c | ||
sparc_v8_irq.c | ||
sparc_v8_registerdump.c | ||
sparc_v8_romgetc.c | ||
sparc_v8_saveusercontext.c | ||
sparc_v8_schedulesigaction.c | ||
sparc_v8_sigdeliver.c | ||
sparc_v8_swint1.c | ||
sparc_v8_switchcontext.c | ||
sparc_v8_syscall.S | ||
sparc_v8_systemreset.c | ||
sparc_v8.h | ||
Toolchain.defs |