rt-thread.git/src/utest/smp, branch v5.3.0-beta

fix: stabilize smp_bind_affinity_tc on SMP CI

2026-06-17T01:51:13Z

This change fixes intermittent failures of the `core.smp_bind_affinity` utest across SMP CI targets. The original failure was a flaky assertion on unbound threads (`thread_inc[x] != thread_tic[x]` in thread_entry), not incorrect bind_cpu behavior. CI logs already showed T0 binding worked (thread_inc[0] == thread_tic[0] == 100) while the not_equal check failed. The root issue is that unbound-thread CPU placement is platform-dependent and outside the bind_cpu contract. On dual-core RISC-V/ARMv7 CI, an unbound thread may legitimately run all iterations on core 0 while T0 delays on the same core, so any assertion requiring cross-core migration (thread_inc != thread_tic, or core_mask with multiple bits) remains flaky. This patch narrows the test to what bind_affinity actually verifies: T0 bound to core 0 must always execute on core 0. Unbound threads only add scheduling pressure; their core_mask is printed for observation but not asserted. Changes: - Sample `rt_hw_cpu_id()` and update counters under `rt_sched_lock` to avoid migration skew between counting and CPU sampling. - Track `thread_core_mask` for diagnostics; assert only T0 binding via `thread_inc[0] == thread_tic[0]` and `thread_core_mask[0] == 1`. - Remove flaky unbound-thread assertions (`thread_inc != thread_tic` and multi-core core_mask checks). - Move T0 assertions to the main test thread after all workers finish. - Use atomic `finsh_flag`; reset counters and `threads[]` in `utest_tc_init`. - Spin in worker loops after `run_num` until cleanup deletes them (do not return from thread_entry or use `RT_WAITING_FOREVER` with `rt_thread_delay`). - Guard `rt_thread_delete` in cleanup with non-NULL checks. Signed-off-by: GuEe-GUI <2991707448@qq.com>

[bsp][zynqmp-a53-dfzu2eg] enable full dm

2026-06-08T06:57:37Z

This is a builtin fdt example BSP Signed-off-by: GuEe-GUI <2991707448@qq.com>

[utest][smp]Add descriptions for the SMP test cases (interrupt_pri and spinlock) #11011

2025-12-11T03:14:43Z

[docs][utest]:Add comments for smp_thread_preemption

2025-12-10T09:06:41Z

Add comments for smp_thread_preemption. Signed-off-by: Mengchen Teng

[utest]:Modify the execution logic of smp_thread_preemptions

2025-12-10T09:06:41Z

Currently, the print information of this test case fails to demonstrate that the high-priority thread has preempted the low-priority thread. This is because when the high-priority thread prints the thread list, there is no information about the low-priority thread (tlow), as tlow has already completed execution and been destroyed. Therefore, the current execution logic cannot confirm the successful completion of the preemption operation. Solution: After the low-priority thread (tlow) releases the lock, add a busy-wait loop while(!finish_flag);. At this point, when the high-priority thread (thigh) prints the thread list information, tlow can be observed in the ready state, indicating that it has been preempted by thigh. Signed-off-by: Mengchen Teng

[utest]: Solve the address misalignment issue of atomic operations

2025-12-04T03:17:50Z

In smp_assigned_idle_cores_tc, the finish_flag involves atomic operations and thus requires address alignment. Signed-off-by: Mengchen Teng

[docs][utest]:Add comments for smp_bind_affinity

2025-11-26T14:51:25Z

Add comments for smp_bind_affinity, And fixed some comment issues in smp_affinity_pri2_tc. Signed-off-by: Mengchen Teng

[docs][utest]:Add comments for smp_affinity_pri2

2025-11-26T14:51:25Z

Add comments for smp_affinity_pri2 Signed-off-by: Mengchen Teng

[docs][utest]:Add comments for smp_affinity_pri1

2025-11-26T14:51:25Z

Add comments for smp_affinity_pri1 Signed-off-by: Mengchen Teng

[docs][utest]:Add explanatory comments for the utest of thread allocation for idle harts

2025-11-19T08:15:47Z

Add explanatory comments for the utest of smp_assigned_idle_cores. Signed-off-by: Mengchen Teng