Lines Matching refs:stack

42   assume that the kernel stack is in a fit state to be used.  Mainly
43   because PAL may or may not maintain the stack pointer internally.
44   Because the MCA/INIT handlers cannot trust the kernel stack, they
50   the kernel stack[1].  So switching to a new kernel stack means that
53   stack also means a new value for current.
73   switches to an MCA/INIT stack, registers its new stack using
82   own stack as running on that cpu.  Then a recursive error gets a
133   stack, so switching stack means switching task.
138   kernel stack.
152 OS has no idea what unwind data is available for the user space stack,
156 stack.  Also the OS has no idea how big the user space RSE and memory
158 mode stack.
166 verifies the original kernel stack, copies the dirty registers from
167 the MCA/INIT stack's RSE to the original stack's RSE, copies the
168 skeleton struct pt_regs and switch_stack to the original stack, fills
170 original stack's thread.ksp.  That makes the original stack look
181 state, then sos->prev_task on the MCA/INIT stack is updated to point to
186 The sos data is always in the MCA/INIT handler stack, at offset