Lines Matching refs:stack

14 Like all other architectures, x86_64 has a kernel stack for every
17 zombie. While the thread is in user space the kernel stack is empty
25 * Interrupt stack.  IRQ_STACK_SIZE
29   kernel switches from the current task to the interrupt stack.  Like
32   of every per thread stack.
34   The interrupt stack is also used when processing a softirq.
36 Switching to the kernel interrupt stack is done by software based on a
41 to automatically switch to a new stack for designated events such as
46 point to dedicated stacks; each stack can be a different size.
50 loads such a descriptor, the hardware automatically sets the new stack
53 will switch back to the per-thread stack.  If software wants to allow
60 NMI.  arch/x86_64/kernel/entry.S::paranoidentry adjusts the stack
63 stack size allocated to an IST assumes no nesting for the same code.
73   when the kernel is very confused (e.g. kernel stack pointer corrupt).
74   Using a separate stack allows the kernel to recover from it well enough
83   assumptions about the previous state of the kernel stack.
93   stack.
97   so a nested #DB starts from a clean stack. The nested #DB switches
106   assumptions about the previous state of the kernel stack.
121 We always scan the full kernel stack for return addresses stored on
122 the kernel stack(s) [1]_, from stack top to stack bottom, and print out
132    values on the kernel stack, from earlier function calls. This is
141 entries printed are strictly in stack order, so you can deduce more
145 information: we always strive to print _all_ addresses on the stack(s)
151        the right order, and try to cross from one stack into another