Lines Matching +full:interrupt +full:- +full:based

1 .. SPDX-License-Identifier: GPL-2.0
7 Kernel stacks on x86-64 bit
25 * Interrupt stack.  IRQ_STACK_SIZE
28   hardware interrupt (i.e. not a nested hardware interrupt) then the
29   kernel switches from the current task to the interrupt stack.  Like
30   the split thread and interrupt stacks on i386, this gives more room
31   for kernel interrupt processing without having to increase the size
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
37 per CPU interrupt nest counter. This is needed because x86-64 "IST"
43 events on x86_64.  This feature is called the Interrupt Stack Table
48 An IST is selected by a non-zero value in the IST field of an
49 interrupt-gate descriptor.  When an interrupt occurs and the hardware
51 pointer based on the IST value, then invokes the interrupt handler.  If
52 the interrupt came from user mode, then the interrupt handler prologue
53 will switch back to the per-thread stack.  If software wants to allow
55 entry to and exit from the interrupt handler.  (This is occasionally
59 nested.  For example, a debug interrupt can safely be interrupted by an
70   Used for interrupt 8 - Double Fault Exception (#DF).
79   Used for non-maskable interrupts (NMI).
87   Used for hardware debug interrupts (interrupt 1) and for software
102   Used for interrupt 18 - Machine Check Exception (#MC).
119 Adapted from Ingo's mail, Message-ID: <20150521101614.GA10889@gmail.com>:
131  - either the address is not part of the call chain: it's just stale
135  - or it is part of the call chain, but the frame pointer was not set
140 or not - but in most cases we'll get the call chain right as well. The
147 we still print out the real call chain as well - just with more question