Lines Matching refs:kernel

8 Like all other architectures, x86_64 has a kernel stack for every
11 zombie. While the thread is in user space the kernel stack is empty
15 associated with each CPU.  These stacks are only used while the kernel
23   kernel switches from the current task to the interrupt stack.  Like
25   for kernel interrupt processing without having to increase the size
30 Switching to the kernel interrupt stack is done by software based on a
54 NMI.  arch/x86_64/kernel/entry.S::paranoidentry adjusts the stack
67   when the kernel is very confused (e.g. kernel stack pointer corrupt).
68   Using a separate stack allows the kernel to recover from it well enough
75   NMI can be delivered at any time, including when the kernel is in the
77   assumptions about the previous state of the kernel stack.
84   When debugging a kernel, debug interrupts (both hardware and
86   avoids making assumptions about the previous state of the kernel
93   MCE can be delivered at any time, including when the kernel is in the
95   assumptions about the previous state of the kernel stack.
106 arch/x86/kernel/dumpstack.c.
110 We always scan the full kernel stack for return addresses stored on
111 the kernel stack(s) [*], from stack top to stack bottom, and print out
112 anything that 'looks like' a kernel text address.
121    values on the kernel stack, from earlier function calls. This is
135 that look like kernel text addresses, so if debug information is wrong,