Skip to content

testing/ostest: spinlock test fixes #3936

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Fix-Point wants to merge 6 commits into
base: master
Choose a base branch
from
+237 −37
Open

testing/ostest: spinlock test fixes #3936

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
65dc344
ostest/spinlock: Fix the affinity side-affect.
Fix-Point Feb 4, 2026
20b6f92
ostest/spinlock: Update the comments.
Fix-Point Feb 5, 2026
b92e572
ostest/spinlock: Add Kconfig option for test thread priority
txy-21 Apr 1, 2026
6af34fa
testing/ostest: fix spinlock test loop count to match Kconfig descrip…
Fix-Point Apr 28, 2026
c17841d
testing/ostest: lower spinlock loop scale under MM_KASAN
Fix-Point Apr 28, 2026
bd96293
testing/ostest: resolve Tasking warning W597 alignment
zyfeier May 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions testing/ostest/Kconfig
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,17 @@ config TESTING_OSTEST_SPINLOCK_THREADS
default 2
range 1 32

config TESTING_OSTEST_SPINLOCK_PRIORITY
int "Priority of spinlock test threads"
default 255
range 1 255
---help---
Priority for spinlock test threads. Default is 255
(SCHED_PRIORITY_MAX). On systems with watchdog monitoring
(e.g., BMP with WdgM), using 255 may starve the watchdog
feeding task and trigger a system reset. Set this below
the watchdog task priority if needed.

config TESTING_OSTEST_MULTIUSER
bool "Multi-user identity and permission tests"
default n
Expand All @@ -144,6 +155,16 @@ config TESTING_OSTEST_MULTIUSER

config TEST_LOOP_SCALE
int "Loop scale of spinlock test (N x 10,000)"
default 5 if MM_KASAN
default 100
---help---
Number of iterations per spinlock test thread, expressed as
scale * 100000 (see LOOP_TIMES in spinlock.c). When KASAN is
enabled the per-lock kasan_check_report overhead serializes
through the global kasan spinlock, slowing each op by orders
of magnitude on single-core QEMU/emulator builds. Use a much
smaller default under MM_KASAN so the test completes within
test-runner timeouts. Non-KASAN builds keep the original 100
scale for meaningful throughput measurement.

endif # TESTING_OSTEST
Loading
Loading