nuttx/drivers/syslog
hujun5 e4d0f404f1 driver: There is no need to use sched_[un]lock
purpose:
1 sched_lock is very time-consuming, and reducing its invocations can improve performance.
2 sched_lock is prone to misuse, and narrowing its scope of use is to prevent people from referencing incorrect code and using 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

We have also tested this patch on other ARM hardware platforms.

Signed-off-by: hujun5 <hujun5@xiaomi.com>
2024-04-30 11:35:13 -03:00
..
CMakeLists.txt
Kconfig
Make.defs
ramlog.c
syslog_channel.c
syslog_chardev.c
syslog_console.c
syslog_consolechannel.c
syslog_devchannel.c
syslog_device.c driver: There is no need to use sched_[un]lock 2024-04-30 11:35:13 -03:00
syslog_filechannel.c driver: There is no need to use sched_[un]lock 2024-04-30 11:35:13 -03:00
syslog_flush.c
syslog_initialize.c
syslog_intbuffer.c
syslog_putc.c
syslog_rpmsg_server.c
syslog_rpmsg.c
syslog_rpmsg.h
syslog_stream.c
syslog_write.c
syslog.h
vsyslog.c