f08c9fe2c2
The syscall stress test relies on timeslicing to switch between threads, which utilizes the interrupt handling path to perform context switching. It is also possible for kernel to switch threads due to, for example, taking a mutex. This adds a bit of code to the syscalls test to simulate this by yielding while inside syscall handlers. This is to cover more scenarios so we can catch issues earlier. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
24 lines
539 B
YAML
24 lines
539 B
YAML
common:
|
|
platform_exclude:
|
|
- qemu_arc/qemu_arc_em
|
|
# Too few MPU regions for USERSPACE testing
|
|
- numaker_m2l31ki
|
|
filter: CONFIG_ARCH_HAS_USERSPACE
|
|
arch_exclude:
|
|
- posix
|
|
tags:
|
|
- kernel
|
|
- security
|
|
- userspace
|
|
ignore_faults: true
|
|
timeout: 180
|
|
tests:
|
|
kernel.memory_protection.syscalls.timeslicing:
|
|
extra_configs:
|
|
- CONFIG_TIMESLICING=y
|
|
- CONFIG_TIMESLICE_SIZE=20
|
|
kernel.memory_protection.syscalls.kyield:
|
|
extra_configs:
|
|
- CONFIG_TIMESLICING=y
|
|
- CONFIG_TIMESLICE_SIZE=0
|