Lines Matching refs:in

47 	However, if the offending CPU does not detect its own stall in
58 	in jiffies.  An RCU-tasks stall warning starts wtih the line:
89 CPUs -and- tasks, in which case the offending CPUs and tasks will all
90 be called out in the list.
97 This is rare, but does happen from time to time in real life.  It is also
98 possible for a zero-jiffy stall to be flagged in this case, depending
127 in dyntick-idle mode and an odd-numbered value otherwise.  The hex
129 be a small positive number if in the idle loop and a very large positive
137 example, if the CPU might have been in dyntick-idle mode for an extended
142 the stalled CPU is spinning with interrupts are disabled, or, in -rt
146 low-order 16 bits (in hex) of the jiffies counter when this CPU last
160 Starving the grace-period kthreads of CPU time can of course result in
177 "What caused it?"  The following problems can result in RCU CPU stall
180 o	A CPU looping in an RCU read-side critical section.
183 	result in RCU-sched and RCU-bh stalls.
186 	result in RCU-sched stalls and, if ksoftirqd is in use, RCU-bh
190 	result in RCU-sched and RCU-bh stalls.
192 o	For !CONFIG_PREEMPT kernels, a CPU looping anywhere in the
195 	if the looping in the kernel is really expected and desirable
200 	This can result in the "All QSes seen" console-log message.
204 o	A CPU-bound real-time task in a CONFIG_PREEMPT kernel, which might
205 	happen to preempt a low-priority task in the middle of an RCU
208 	in which case the next RCU grace period can never complete, which
210 	While the system is in the process of running itself out of
213 o	A CPU-bound real-time task in a CONFIG_PREEMPT_RT kernel that
216 	and in a CONFIG_PREEMPT_RCU kernel will further prevent
223 	interrupt on a CPU that is not in dyntick-idle mode.  This
225 	result in RCU CPU stall warnings for CONFIG_NO_HZ_COMMON=n kernels.
227 o	A bug in the RCU implementation.
230 	at least once in real life.  A CPU failed in a running system,
232 	This resulted in a series of RCU CPU stall warnings, eventually
237 that RCU only detects CPU stalls when there is a grace period in progress.
244 is occurring, which will usually be in the function nearest the top of