AArch64: Do not use CONFIG_GEN_PRIV_STACKS
We are setting CONFIG_GEN_PRIV_STACKS when AArch64 actually uses a statically allocated privileged stack. This error was not captured by the tests because we only verify whether a read/write to a privileged stack is failing, but it can fail for a lot of reasons including when the pointer to the privileged stack is not initialized at all, like in this case. With this patch we deselect CONFIG_GEN_PRIV_STACKS and we fix the mem_protect/userspace test to correctly probe the privileged stack. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
This commit is contained in:
parent
1b41da2630
commit
807991e15f
3 changed files with 18 additions and 3 deletions
|
@ -47,4 +47,12 @@
|
|||
#define ARCH_KERNEL_STACK_RESERVED 0
|
||||
#define ARCH_KERNEL_STACK_OBJ_ALIGN ARCH_STACK_PTR_ALIGN
|
||||
|
||||
#ifndef _ASMLANGUAGE
|
||||
|
||||
struct z_arm64_thread_stack_header {
|
||||
char privilege_stack[CONFIG_PRIVILEGED_STACK_SIZE];
|
||||
} __packed __aligned(Z_ARM64_STACK_BASE_ALIGN);
|
||||
|
||||
#endif /* _ASMLANGUAGE */
|
||||
|
||||
#endif /* ZEPHYR_INCLUDE_ARCH_ARM_AARCH64_THREAD_STACK_H_ */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue