arch: riscv: IRQ stacks of secondary cores are not initialized to 0xAA
when CONFIG_INIT_STACKS=y
#78244
Labels
area: RISCV
RISCV Architecture (32-bit & 64-bit)
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Describe the bug
Currently, the IRQ stacks of secondary cores are not initialized to
0xAA
whenCONFIG_INIT_STACKS=y
, this results in the watermark not being correctly computed by Zephyr, which can be seen by doingkernel thread stacks
. This issue also exists in at least v3.5.0 and earlier.Not sure if this has any other implications, other that the
kernel thread stacks
not displaying the watermark correctly.To Reproduce
main
branchwest build -b qemu_riscv64_smp -p auto -t run zephyr/samples/hello_world -- -DCONFIG_SHELL=y
kernel thread stacks
IRQ 01
++ stacks, the usage is always at 100%Expected behavior
The usage should reflect the real watermark of the IRQ stack, which should be much lesser than 100%
Impact
z_stack_space_get
will return the actual usage of secondary cores' IRQ stackAdditional context
#78053
The text was updated successfully, but these errors were encountered: