Lines Matching full:period

40 -	Anything that prevents RCU's grace-period kthreads from running.
51 	in which case the next RCU grace period can never complete, which
119 RCU only detects CPU stalls when there is a grace period in progress.
120 No grace period, no CPU stall warnings.
148 	This kernel configuration parameter defines the period of time
149 	that RCU will wait from the beginning of a grace period until it
150 	issues an RCU CPU stall warning.  This time period is normally
169 	the expedited grace period. This parameter defines the period
171 	grace period until it issues an RCU CPU stall warning. This time
172 	period is normally 20 milliseconds on Android devices.	A zero
216 	task stalling the current RCU-tasks grace period.
243 interrupts during the current stalled grace period.
256 last noted the beginning of a grace period, which might be the current
257 (stalled) grace period, or it might be some earlier grace period (for
259 time period).  The number after the "/" is the number that have executed
267 detection passes that the grace-period kthread has made across this
269 period.
273 period (in this case 2603), the grace-period sequence number (7075), and
277 If the grace period ends just as the stall warning starts printing,
285 on how the stall warning and the grace-period initialization happen to
291 grace period has nevertheless failed to end, the stall-warning splat
297 since the grace-period kthread ran.  The "jiffies_till_next_fqs"
303 If the relevant grace-period kthread has been unable to run prior to
310 Starving the grace-period kthreads of CPU time can of course result
313 grace-period sequence number, the "f" precedes the ->gp_flags command
314 to the grace-period kthread, the "RCU_GP_WAIT_FQS" indicates that the
316 task_struct ->state field, and the "cpu" indicates that the grace-period
319 If the relevant grace-period kthread does not wake from FQS wait in a
332 Here "cpu" indicates that the grace-period kthread last ran on CPU 4,
352 stack dumps for the different messages for the same stalled grace period.
358 If an expedited grace period detects a stall, it will place a message
365 is online (otherwise the first period would instead have been "O"),
366 that the CPU was online at the beginning of the expedited grace period
367 (otherwise the second period would have instead been "o"), and that
369 period would instead have been "N").  The number before the "jiffies"
370 indicates that the expedited grace period has been going on for 21,119
372 grace-period sequence counter is 73.  The fact that this last value is
373 odd indicates that an expedited grace period is in flight.  The number
376 current expedited grace period.  If the tree had more than one level,