1104 Commits

Author	SHA1	Message	Date
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
Pillar	b084503b6d	[kernel] add UP scheduler critical switch flag.	2025-08-06 15:53:18 +08:00
Yuqiang Wang	62f3fb4ce5	fix(kernel)/improve(utest):fix the legacy issue related to the length of the object name version #10537	2025-07-30 10:58:49 +08:00
Chen Wang	3c046646cb	doxygen: promote object management to a separate page ... For "RT-Thread User Guide": Take the "RT-Thread Kernel Object Model" sub-section out of the "Kernel Basics" section and rename it to "Object Management". Correspondingly, rename the "Kernel Object Management" section in the "RT-Thread API Guide" to "Object Management". Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-07-22 18:07:17 +08:00
kurisaw	ece19e961a	kernel/testcase: fixed buffer overflow vulnerability in object	2025-07-18 20:15:53 +08:00
Yulong Wang	136ef85ba3	[signal]: fix spinlock leak in rt_thread_handle_sig()	2025-07-08 14:14:54 +08:00
Yulong Wang	b2ce955126	Remove extra semicolon in src/memheap.c	2025-06-27 16:52:33 +08:00
Chen Wang	8e9872a554	doxygen: group name all in lowcase ... This patch only updated the groups defined in documentation/0.doxygen. Other groups will be moved into documentation/0.doxygen and updated at that time. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-06-25 14:02:28 +08:00
Guorui Li	f5bff56c5b	[kernel]add doxygen comments for scheduler. (#10366) ... * [kernel]add doxygen comments for scheduler. * [kernel]fix spell error in comments.	2025-06-08 15:03:26 +08:00
htl5241	31ff6fecc1	[clock]添加 rt_tick_get_delta 函数	2025-05-23 14:21:37 +08:00
Chen Wang	55428e4393	doxygen: re-org module groups (#10197) ... Match the organization of modules (groups) with that of user guide. Preliminary arrangement. This patch is just a framework arrangement. Details need to be continued. P.S., in this patch, adding numerical prefixes to the files in documentation/0.doxygen is to meet the need of displaying sorting in HTML pages. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-04-18 10:44:43 +08:00
wycwyhwyq	12de72a462	add RT_THREAD_CTRL_SET_PRIORITY	2025-04-13 15:25:42 +08:00
wycwyhwyq	da1c5c7882	add RT_THREAD_CTRL_SET_PRIORITY	2025-04-13 15:25:42 +08:00
wycwyhwyq	f13193ff92	[src] fix mutex bug	2025-04-13 15:25:42 +08:00
kk	4acef9b1cd	Update include/rtdef.h version to 5.2.1	2025-03-28 23:12:14 -04:00
latercomer	e91131bc0d	解决__RT_KERNEL_SOURCE__宏没有定义 ... Signed-off-by: latercomer <latercomer@qq.com>	2025-03-17 16:45:59 +08:00
latercomer	76c2f2d77f	解决bps/simulator无法在vs2019环境下编译 ... Signed-off-by: latercomer <latercomer@qq.com>	2025-03-17 16:45:59 +08:00
yixinghua121	983f02151a	修复 MMCSD 宏拼写错误+内核开启LOG_D编译问题	2025-03-12 16:02:43 +08:00
Chen Wang	5a42cfd16b	doxygen: update doc for kenrel object model ... Move the introduction of function parameters in markdown to source code comments, because this part of the content is completely repeated. We only need to keep and maintain the comments in the code. The detailed explanation of the API in markdown can directly refer to the comments in the code. Try not to directly copy the definition of the structure in the markdown document, because this part of the content may change with the upgrade of the code. Therefore, when the structure definition is involved in markdown, try to indicate that it is just a code snippet. The specific definition is still directly quoted from the source code and the source code comments. It is very convenient to quote structures and functions in markdown. Just use "`" to enclose the structure name or function name, and the generated html is a link to its definition. According to this principle, this patch only modifies the documents and code comments of the kernel object model. Other modules will be modified one by one in separate patches later. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-03-12 12:54:25 +08:00
Yuqiang Wang	ad79383fa3	feat: ci script associated with auto_utest. (#9933) ... * feat: ci script associated with auto_utest.	2025-03-10 11:08:21 +08:00
Shell	d9b36c8d18	feat: improve Kconfig structure on MM ... Signed-off-by: Shell <smokewood@qq.com>	2025-02-25 11:26:30 +08:00
Shell	60f7b3affc	feat: mm: page poison debugging and assertion enhancements ... This commit introduces a page poison debugging mechanism and additional assertions for memory management, improving system maintainability and debugging capabilities. The changes aim to detect illegal memory usage early and provide better clarity in managing page allocations. Changes: - Added `RT_DEBUGGING_PAGE_POISON` option to enable memory usage tracing. - Introduced a page poisoner for detecting illegal memory usage. - Implemented region-based memory tracking using bitmaps. - Enhanced spinlock protection for memory management operations. - Fixed several assertion checks for memory safety. - Renamed macros for consistency (`FLOOR` to `CEIL`). - Refined memory allocation and deallocation logic to include poisoning. - Updated Kconfig to add configurable `RT_PAGE_MAX_ORDER` and poison debugging. - Improved debugging outputs for page regions and memory operations. Signed-off-by: Shell <smokewood@qq.com>	2025-02-25 11:26:30 +08:00
Supper Thomas	5b3320624d	[src/ktime] fix the bug when use keil AC6 and open RT_USING_HOOKLIST … (#9993) ... * [src/ktime] fix the bug when use keil AC6 and open RT_USING_HOOKLIST and RT_USING_KTIME	2025-02-16 22:02:42 +08:00
Chen Wang	c40b79037c	doxygen: add prefix for groups (#9991) ... * doxygen: add prefix for groups Add "group_" prefix to doxygen group names. This makes it easier to grep with group name later. This patch only modifies the groups defined in the pathes of INPUT of documentation/Doxyfile: INPUT = . \ ../src \ ../include \ ../components/finsh \ ../components/drivers/include/drivers \ ../components/drivers/clk \ ../components/dfs/dfs_v2/src \ ../components/dfs/dfs_v2/include Other groups are not touched. Signed-off-by: Chen Wang <unicorn_wang@outlook.com> * ci: fixed error report when run file_check.py Such as: - "please delete extra space at the end of this line." - "the RT-Thread error code should return negative value. e.g. return -RT_ERROR" Signed-off-by: Chen Wang <unicorn_wang@outlook.com> --------- Signed-off-by: Chen Wang <unicorn_wang@outlook.com>	2025-02-15 12:15:19 +08:00
Meco Man	bdd9447d70	[utest] make RT_USING_CI_ACTION to be clear ... RT_USING_CI_ACTION will select RT_UTEST_USING_AUTO_RUN and RT_UTEST_USING_ALL_CASES	2025-01-09 17:45:15 -05:00
Meco Man	97b9cc5000	fix: add \n for addr2line hint	2025-01-08 17:54:46 -05:00
Meco Man	0a25fcffab	[utest] add float operators ... uassert_float_equal and uassert_float_not_equal	2025-01-07 20:44:29 -05:00
Meco Man	6cad23bc31	[kservice] optimize console_device	2025-01-04 22:50:04 -05:00
Meco Man	b3b99082f9	[rt_vsscanf] upgrade version and add test case ... from: https://github.com/phoenix-rtos/libphoenix/blob/master/stdio/scanf.c BSD-3-Clause license	2025-01-04 18:07:05 +08:00
Meco Man	d583615afe	[utest] add rt_memset test case	2025-01-03 13:42:21 +08:00
Meco Man	8c762b42ca	[utest] implement rt_memcmp test cases	2024-12-24 13:42:04 +08:00
Meco Man	a803c20bd7	[utest] implement more test case for rt_memcpy	2024-12-24 13:42:04 +08:00
Meco Man	61d62ab358	[utest] remove rt_kprintf from TC_rt_sprintf.c	2024-12-24 13:42:04 +08:00
Meco Man	c9ed784131	[utest][klibc] add rt_sprintf family functions test cases	2024-12-22 23:12:02 -05:00
Meco Man	fc1abf46a9	[utest] add rt_memcpy utest case	2024-12-21 14:57:17 -05:00
guozhanxin	7fb9a0a3bb	[kernel] change size_t to rt_size_t	2024-12-18 19:31:38 -05:00
wdfk-prog	ec900a7135	fix:[klib]Kconfig显示文案错误	2024-12-07 23:23:03 -05:00