tests/kernel: Bump kobj thread bitmask size for a few tests

A scheduler fix for free memory usage on aborted threads is now using
a per-CPU dummy thread instead of a single stack-based one at startup.
These static thread objects need spots in the kobj bitmasks, and a few
tests are sitting right at the default limit (16 threads).

Signed-off-by: Andy Ross <andyross@google.com>
This commit is contained in:
Andy Ross 2024-04-06 11:53:30 -07:00 committed by Anas Nashif
commit cef2ac5583
4 changed files with 4 additions and 0 deletions

View file

@ -15,6 +15,7 @@ CONFIG_MAIN_STACK_SIZE=2048
CONFIG_ENTROPY_GENERATOR=y CONFIG_ENTROPY_GENERATOR=y
CONFIG_TEST_RANDOM_GENERATOR=y CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_INIT_STACKS=y CONFIG_INIT_STACKS=y
CONFIG_MAX_THREAD_BYTES=3
# Logging # Logging
CONFIG_NET_LOG=y CONFIG_NET_LOG=y

View file

@ -6,3 +6,4 @@ CONFIG_BOOT_DELAY=500
CONFIG_IRQ_OFFLOAD=y CONFIG_IRQ_OFFLOAD=y
CONFIG_TEST_USERSPACE=y CONFIG_TEST_USERSPACE=y
CONFIG_BOUNDS_CHECK_BYPASS_MITIGATION=y CONFIG_BOUNDS_CHECK_BYPASS_MITIGATION=y
CONFIG_MAX_THREAD_BYTES=3

View file

@ -3,3 +3,4 @@ CONFIG_IRQ_OFFLOAD=y
CONFIG_TEST_USERSPACE=y CONFIG_TEST_USERSPACE=y
CONFIG_ZTEST_FATAL_HOOK=y CONFIG_ZTEST_FATAL_HOOK=y
CONFIG_PIPES=y CONFIG_PIPES=y
CONFIG_MAX_THREAD_BYTES=3

View file

@ -1,3 +1,4 @@
CONFIG_ZTEST=y CONFIG_ZTEST=y
CONFIG_TEST_USERSPACE=y CONFIG_TEST_USERSPACE=y
CONFIG_ZTEST_FATAL_HOOK=y CONFIG_ZTEST_FATAL_HOOK=y
CONFIG_MAX_THREAD_BYTES=3