Lines Matching full:tasks

125 The RCU, RCU-sched, RCU-tasks, and RCU-tasks-trace implementations have
216 	This boot/sysfs parameter controls the RCU-tasks and
217 	RCU-tasks-trace stall warning intervals.  A value of zero or less
218 	suppresses RCU-tasks stall warnings.  A positive value sets the
219 	stall-warning interval in seconds.  An RCU-tasks stall warning
222 		INFO: rcu_tasks detected stalls on tasks:
225 	task stalling the current RCU-tasks grace period.
227 	An RCU-tasks-trace stall warning starts (and continues) similarly:
229 		INFO: rcu_tasks_trace detected stalls on tasks
235 For non-RCU-tasks flavors of RCU, when a CPU detects that some other
238 	INFO: rcu_sched detected stalls on CPUs/tasks:
246 PREEMPT_RCU builds can be stalled by tasks as well as by CPUs, and that
247 the tasks will be indicated by PID, for example, "P3421".  It is even
248 possible for an rcu_state stall to be caused by both CPUs *and* tasks,
249 in which case the offending CPUs and tasks will all be called out in the list.
304 If all CPUs and tasks have passed through quiescent states, but the
325 in RCU CPU stall warnings even when all CPUs and tasks have passed
352 These messages are usually followed by stack dumps of the CPUs and tasks
375 	INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 7-... } 21119 jiffies s: 73 root: 0x2/.
389 rcu_node structure correspond to CPUs and/or tasks that are blocking the
395 tasks as well as by CPUs, and that the tasks will be indicated by PID,
416 milliseconds consumed by hard interrupts, soft interrupts, and tasks
418 in milliseconds.  Because user-mode tasks normally do not cause RCU CPU
419 stalls, these tasks are typically kernel tasks, which is why only the