Lines Matching refs:INIT

1 An ad-hoc collection of notes on IA64 MCA and INIT processing.  Feel
6 MCA/INIT are completely asynchronous.  They can occur at any time, when
8 holding a spinlock.  Trying to get any lock from MCA/INIT state is
29   sends an unmaskable INIT event to the slave cpus that have not
32 * Because MCA/INIT can be delivered at any time, including when the cpu
34   event are _completely_ undefined.  In particular the MCA/INIT
37   TP on return.  However MCA/INIT events expose us to these PAL
40 * If an MCA/INIT event occurs while the kernel was running (not user
41   space) and the kernel has called PAL then the MCA/INIT handler cannot
44   Because the MCA/INIT handlers cannot trust the kernel stack, they
45   have to use their own, per-cpu stacks.  The MCA/INIT stacks are
67   INIT event are no longer running, they have been converted to blocked
73   switches to an MCA/INIT stack, registers its new stack using
78 * MCA/INIT can be nested, to a depth of 2 on any cpu.  In the case of a
79   nested error, we want diagnostics on the MCA/INIT handler that
81   requires set_curr_task() so the MCA/INIT handlers can register their
86     struct task and the kernel stacks.  Then the MCA/INIT data would be
91     stacks meant separate "tasks" for the MCA/INIT handlers.
95 INIT is less complicated than MCA.  Pressing the nmi button or using
96 the equivalent command on the management console sends INIT to all
98 slaves.  All the OS INIT handlers are entered at approximately the same
107 SAL on resume.  The OS INIT code has workarounds for some of these
113 violations.  Unfortunately MCA/INIT start off as massive layer
123 How is ia64 MCA/INIT different from x86 NMI?
125 * x86 NMI typically gets delivered to one cpu.  MCA/INIT gets sent to
128 * x86 NMI cannot be nested.  MCA/INIT can be nested, to a depth of 2
136   about any registers having changed.  MCA/INIT can occur while the cpu
146 What happens when MCA/INIT is delivered what a cpu is running user
149 The user mode registers are stored in the RSE area of the MCA/INIT on
151 mode registers are preserved across a recoverable MCA/INIT.  Since the
153 MCA/INIT never tries to backtrace user space.  Which means that the OS
162 How do we get a backtrace on the tasks that were running when MCA/INIT
167 the MCA/INIT stack's RSE to the original stack's RSE, copies the
177 How do we identify the tasks that were running when MCA/INIT was
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
191 Also the comm field of the MCA/INIT task is modified to include the pid