Lines Matching refs:task

46   preformatted with just enough task state to let the relevant handlers
49 * Unlike most other architectures, the ia64 struct task is embedded in
51   we switch to a new task as well.  Because various bits of the kernel
52   assume that current points into the struct task, switching to a new
63 * The starting point for the unwind depends on whether a task is
65   monarch has to determine whether or not a task is on a cpu before it
74   set_curr_task(), so the monarch can tell that the _original_ task is
76   getting a valid backtrace of the _original_ task.
80   failed, not on the task that was originally running.  Again this
83   trace of the failing handler's "task".
86     struct task and the kernel stacks.  Then the MCA/INIT data would be
131 * x86 has a separate struct task which points to one of multiple kernel
132   stacks.  ia64 has the struct task embedded in the single kernel
133   stack, so switching stack means switching task.
154 does not bother making the user space process look like a blocked task,
171 exactly like any other blocked task, i.e. it now appears to be
173 original task and unwind like any other sleeping task.
180 If the previous task has been verified and converted to a blocked
182 the previous task.  You can look at that field in dumps or debuggers.
191 Also the comm field of the MCA/INIT task is modified to include the pid
192 of the original task, for humans to use.  For example, a comm field of