1140 Commits

Author	SHA1	Message	Date
Copilot	d39a439603	[klibc] 将函数签名与标准 libc 对齐以修复类型冲突 #10890	2025-11-07 15:48:51 +08:00
kurisaw	3559323427	[kernel][object]: update the default value of RT_NAME_MAX to 12	2025-10-23 22:06:51 +08:00
Chen Wang	68a27e1fbe	utest: UTEST_MEMPOOL_TC -> RT_UTEST_MEMPOOL ... Which is missed in PR #10808 "utest: unify configname", add it. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-16 18:34:43 +08:00
Chen Wang	c1363c77d6	utest: Improve the strings displayed in the menu ... Use "Test" instead of "Unit Testcases" to make string shorter. Use uppercase to make it look more eye-catching. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-16 18:34:43 +08:00
Chen Wang	04439c2074	utest: reorg menu items ... The original project display was completely flat, now it is organized into a tree-like hierarchical structure based on the layout of the code. mm & tmpfs test are still keep as pervious bcos we have not move the source for these two components. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-16 18:34:43 +08:00
Chen Wang	58dc730ece	utest: UTEST_SMP_THREAD_PREEMPTION_TC -> RT_UTEST_SMP_THREAD_PREEMPTION ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	d4533b0a17	utest: UTEST_SMP_SPINLOCK_TC -> RT_UTEST_SMP_SPINLOCK ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	647f24bd6d	utest: UTEST_SMP_INTERRUPT_PRI_TC -> RT_UTEST_SMP_INTERRUPT_PRI ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	b89eada804	utest: UTEST_SMP_ASSIGNED_IDLE_CORE_TC -> RT_UTEST_SMP_ASSIGNED_IDLE_CORE ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	b90b29255c	utest: UTEST_SMP_AFFFINITY_TC -> RT_UTEST_SMP_AFFFINITY ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	1dbcde518a	utest: UTEST_SCHEDULER_TC -> RT_UTEST_SCHEDULER ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	5b8bfe4a77	utest: UTEST_MTSAFE_KPRINT_TC -> RT_UTEST_MTSAFE_KPRINT ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	405d096ff3	utest: UTEST_HOOKLIST_TC -> RT_UTEST_HOOKLIST ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	aac9eb8fbd	utest: UTEST_ATOMIC_TC -> RT_UTEST_ATOMIC ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	ff9f1770c7	utest: UTEST_THREAD_TC -> RT_UTEST_THREAD ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	454a0c3a27	utest: UTEST_MAILBOX_TC -> RT_UTEST_MAILBOX ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	78c2acbdae	utest: UTEST_MUTEX_TC -> RT_UTEST_MUTEX ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	68edf1792f	utest: UTEST_SIGNAL_TC -> RT_UTEST_SIGNAL ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	7f17a580ab	utest: UTEST_MESSAGEQUEUE_TC -> RT_UTEST_MESSAGEQUEUE ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	9465d71c29	utest: UTEST_TIMER_TC -> RT_UTEST_TIMER ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	468007dda7	utest: UTEST_EVENT_TC -> RT_UTEST_EVENT ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	f0b6ad057d	utest: UTEST_SEMAPHORE_TC -> RT_UTEST_SEMAPHORE ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	d5ffca9e90	utest: UTEST_IRQ_TC -> RT_UTEST_IRQ ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	2b09fefbb0	utest: UTEST_SLAB_TC -> RT_UTEST_SLAB ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	0eda9bb5f1	utest: UTEST_OBJECT_TC -> RT_UTEST_OBJECT ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	0b8d2b3594	utest: UTEST_SMALL_MEM_TC -> RT_UTEST_SMALL_MEM ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	c2e1d7dee1	utest: UTEST_MEMHEAP_TC -> RT_UTEST_MEMHEAP ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-15 09:43:16 +08:00
Chen Wang	7499790140	utest: core: move perf testcase from example to src ... Also: - Add "RT_" prefix for the UTEST config options. - Follow the naming rules to update the case name. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-10-11 18:24:40 +08:00
Chen Wang	3dd4f71bb6	doxygen: cleanup code for group_thread_management ... The cleanup involved three parts: - Merging the standalone "/**@{*/" into "@addtogroup group_thread_management" - Changing "/**@}*/" to "/** @} group_thread_management */", adding the group name makes it easier to find the matching "@{" part. - Deleting the "@addtogroup" directive in "include/rtthread.h" because this header file doesn't have doxygen comments. All doxygen comments for function bodies are defined in other .c files. Note, we remian two doxygen comments for rt_thread_inited_hookproto_t and rt_thread_idle_sethook in the "include/rtthread.h". rt_thread_inited_hookproto_t is really defined here. For rt_thread_idle_sethook, please see FIXME comment for reason. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-30 10:25:08 +08:00
Chen Wang	05dc189e37	doxygen: cleanup code for group_object_management ... The cleanup involved three parts: - Merging the standalone "/**@{*/" into "@addtogroup group_object_management" - Changing "/**@}*/" to "/** @} group_object_management */", adding the group name makes it easier to find the matching "@{" part. - Deleting the "@addtogroup" directive in "include/rtthread.h" because this header file doesn't have doxygen comments. All doxygen comments for function bodies are defined in "src/object.c". Plus minor cleanup for group_hook in src/object.c. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-29 14:22:40 +08:00
Yuqiang Wang	36393c61be	improve[ci]: integrate utest run ci (#10748)	2025-09-28 16:08:51 +08:00
Chen Wang	01e015450f	utest: move driver related case under to drivers ... src/utest/device_tc.c is testing API: rt_device_find(), which is a function defined in components/drivers/core/device.c. So it should be a testcase for drivers core, not for core. Move it to under components/drivers/core. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-26 16:53:44 +08:00
Chen Wang	adc3e2ccc5	utest: core: unify case names ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-26 09:59:05 +08:00
Chen Wang	6e51a8405f	utest: move core tesetcases under to directiry "src" ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-26 09:59:05 +08:00
Chen Wang	495c8cfc25	utest: remove RT_UTEST_USING_ALL_CASES ... Many modules' utests currently don't support enabling all tests at once. Furthermore, some modules' tests are complex, for example due to their numerous dependencies on other modules. This makes it nearly impossible to enable all tests with a single global switch. Consequently, the previously defined `RT_UTEST_USING_ALL_CASES` has lost its original meaning. We recommend deprecating this configuration switch. If a module needs to enable a group of functional tests through its own configuration, this local enable all switch should be implemented by the module itself, and a global RTT enable switch will no longer be provided. If such a requirement arises in the future, we recommend careful design, especially considering how to ensure that turning on a single switch enables all dependencies for all involved modules for ease of use. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-26 09:57:54 +08:00
Yonggang Luo	66b2bcc080	RT_TIMER_CTRL_SET_TIME only accept rt_tick_t, pass rt_tick_t instead int/rt_int32_t	2025-09-24 18:12:36 +08:00
wdfk-prog	2d375b236c	[kernel]fix scheduling exception caused by interrupt preemption in rt_schedule	2025-09-21 15:26:51 +08:00
Chen Wang	b03bb709b9	utest: update naems using new rule ... The names of the utest cases defined in their respective modules have been updated. Some utest case names are not yet in their respective modules because their paths need to be finalized before their unique names can be determined. Currently, these names do not appear to conflict with the unified names. These include: - utest cases still in examples - bsp/qemu-virt64-riscv/applications/test/test_vector/test_vector.c. The entire test case should probably be placed in libcpu/risc-v rather than bsp. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-15 19:40:31 +08:00
蒙蒙plus	138c8887e7	移除已经废弃的CPU使用率相关的字段和初始化代码	2025-09-12 09:56:16 +08:00
Chen Wang	1034e5b4fd	doxygen: fixed duplicated comments for scheduler APIs ... Similar to PR #10674, `src/scheduler_mp.c` and `src/scheduler_up.c` also have similar issues. After investigation, we found: in commit 2c98ce4605 "[HUST CSE][document] Fix some comments, invalid grouping commands and warnings in Doxygen." This patch excluded `src/scheduler_mp.c` and `src/scheduler_up.c` from the Doxygen build and include `documentation/doxygen/thread.h` (the new file path after adjustment is `documentation/0.doxygen/core/thread.h`), placing the Doxygen comments for some functions in this file. However, this approach has its problems: - The comments in `documentation/0.doxygen/core/thread.h` are separated from the source code, making them difficult to maintain. This also results in the comments for the newly added functions in `src/scheduler_mp.c` and `src/scheduler_up.c` not being updated in a timely manner and failing to be compiled into Doxygen (becoming HTML). - For the average programmer, it's unlikely that they'll consider the `documentation/0.doxygen/` directory for function declarations and comments, let alone the need to maintain the Doxygen comments in that directory. Currently, the header files under `documentation/0.doxygen/` should strictly be used only to define Doxygen groups and should not include Doxygen comments for the code itself. (Similar issues exist in documentation/0.doxygen/3.hardware.h and documentation/0.doxygen/core/systeminit.h, which require further cleanup.) The solution is similar to PR #10674, where only MP documentation is generated by default. For functions defined in MP but not in UP, we use the "@note" directive in the function's doxygen comment to indicate whether the function is supported in both UP and MP, or only in MP. After implementing this solution, the file `documentation/0.doxygen/core/thread.h` can be deleted. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-09 18:20:41 +08:00
Rbb666	e1c1a07c48	[add][thread]Add api:rt_thread_suspend_force allow suspend other threads.	2025-09-09 13:08:30 +08:00
Chen Wang	afb3f22973	doxygen: fixed duplicated comments for cpu APIs ... Refer to the issue described in PR #10599. This was a temporary fix at that time. After further research, we discovered that this issue can be addressed using the "@cond" command supported by Doxygen. Since we currently do not intend to generate two sets of documentation for UP and MP when generating Doxygen documentation, the current solution is to generate only MP documentation by default. For functions defined in MP but not in UP, we will use the "@note" command in the function's Doxygen comment to indicate whether the function supports both UP and MP, or only MP. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-08 22:20:52 +08:00
Chen Wang	f44ce3a64c	doxygen: updated doc for thread management subsystem ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-09-02 18:05:44 +08:00
Rbb666	3c17851fe2	[Add][kernel/thread]Add thread overflow hook and testcases:thread_overflow_tc.c.	2025-09-02 16:46:55 +08:00
Haojin Tang	483117fa14	fix(klibc): also check __clang__ when detecting gcc	2025-09-01 15:39:59 +08:00
maosql	9567564e86	fix: warnings generated by Kconfig.	2025-09-01 11:50:41 +08:00
Rbb666	bc4c036942	[Add][kservice]Add thread usage support.	2025-08-30 13:10:14 +08:00
ryancw	df70e4b9bc	[kernel] rt_scheduler_lock_nest使用原子操作	2025-08-28 11:33:15 +08:00
Chen Wang	532da3482b	utest: integrate config option for utest of klibc ... Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-08-26 10:26:47 +08:00
Chen Wang	715334f357	doxygen: fix build error ... fixed: b084503b6d "[kernel] add UP scheduler critical switch flag." After this commit, doxygen build with warning: include/rtthread.h:658: warning: argument 'lock' from the argument list of rt_spin_unlock has multiple @param documentation sections include/rtthread.h:660: warning: argument 'lock' from the argument list of rt_spin_unlock_irqrestore has multiple @param documentation sections include/rtthread.h:660: warning: argument 'level' from the argument list of rt_spin_unlock_irqrestore has multiple @param documentation sections Rootcasue analysis: src/cpu_up.c and src/cpu_mp.c define two identical functions. Because the INPUT parameter in the documentation/Doxyfile currently compiles all source files under ./src, i.e both of them, Doxygen automatically merges the Doxygen comments for identically named functions if it finds the content of doxygen comments different, resulting in multiple @param. Previously, the API comments in both files were identical, so there was no problem. However, the b084503b6d change only modified the comments in src/cpu_up.c but not in src/cpu_mp.c, causing problems. Another drawback of the b084503b6d change is that Doxygen recommends a single line for the @brief; multiple lines are not recommended. Solution: Given the requirement for a single line for the @brief, this issue is relatively simple to resolve: simply list the extra content as @note. Regarding the warning: A perfect solution has not yet been found. One possible approach is to write a single Doxygen comment for a kernel API with two implementations. This approach involves writing Doxygen comments in only one file, such as src/cpu_up.c , while omitting them in src/cpu_mp.c . Another solution is to add API comments to include/rtthread.h , but the RT-Thread include/rtthread.h file is already quite large, and adding comments there would be even more cumbersome. A temporary solution currently in use is to ensure that the Doxygen comments for the same API are identical in both src/cpu_up.c and src/cpu_mp.c . This ensures that Doxygen compilation does not generate warnings, and the files are automatically merged into a single file in the HTML document. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-08-12 09:14:46 +08:00