testing/ostest/smp_call.c: fix smp_call cpu_set inconsistency issue #3244
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
fix smp_call cpu_set inconsistency issue
If we set CONFIG_SMP_DEFAULT_CPUSET=1
This will cause the value of cpuset to be 0x1,
((1 << CONFIG_SMP_NCPUS) - 1) will result in the cpuset being 0x11, leading to test case errors.
Impact
smpcall test
Testing
testing in hardware
esp32s3-devkit:smp
End of test memory usage:
VARIABLE BEFORE AFTER
======== ======== ========
arena 5ced0 5ced0
ordblks 2 2
mxordblk 57c58 56a88
uordblks 51e0 63b0
fordblks 57cf0 56b20
user_main: smp call test
smp_call_test: Test start
smp_call_test: Call cpu 0, nowait
smp_call_test: Call cpu 0, wait
smp_call_test: Call cpu 1, nowait
smp_call_test: Call cpu 1, wait
smp_call_test: Call multi cpu, nowait
smp_call_test: Call in interrupt, wait
smp_call_test: Call multi cpu, wait
smp_call_test: Test success
user_main: Exiting
ostest_main: Exiting with status 0
nsh> uname -a
NuttX 12.11.0 c8332926cab Dec 9 2025 18:45:30 xtensa esp32s3-devkit
nsh>