Skip to content

Conversation

@hujun260
Copy link
Contributor

@hujun260 hujun260 commented Dec 9, 2025

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>

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.

Signed-off-by: hujun5 <hujun5@xiaomi.com>
Copy link
Contributor

@cederom cederom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @hujun260 :-)

@linguini1 linguini1 merged commit 24e1c4d into apache:master Dec 9, 2025
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants