Andrew Boie 74cbbc9d37 x86: arm: don't force stacks into kernel memory ... This was felt to be necessary at one point but actually isn't. - When a thread is initialized to use a particular stack, calls will be made to the MMU/MPU to restrict access to that stack to only that thread. Once a stack is in use, it will not be generally readable even if the buffer exists in application memory space. - If a user thread wants to create a thread, we will need to have some way to ensure that whatever stack buffer passed in is unused and appropriate. Since unused stacks in application memory will be generally accessible, we can just check that the calling thread to k_thread_create() has access to the stack buffer passed in, it won't if the stack is in use. On ARM we had a linker definition for .stacks, but currently stacks are just tagged with __noinit (which is fine). Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>		2017-09-08 12:26:05 -07:00
..
arc
arm	x86: arm: don't force stacks into kernel memory	2017-09-08 12:26:05 -07:00
nios2
riscv32
x86	x86: arm: don't force stacks into kernel memory	2017-09-08 12:26:05 -07:00
xtensa
cpu.h