Searched refs:infinite (Results 1 – 22 of 22) sorted by relevance
171 int err = 0, i, infinite = !cycles_count; in tort_init() local332 if (!infinite && --cycles_count == 0) in tort_init()
26 when we ERET back to the guest. This causes the guest to hang in an infinite loop.
57 valid values is [0..15], where 0 indicates infinite retries.
110 Otherwise the set of contended objects would be infinite - each of them117 would again have an infinite set of contended objects). But that
110 The default is infinite. Note that the size of read requests is
178 Now this puts kernel into infinite loop after first oops. Till
87 to complete before exiting. Note that if 'iterations' is set to 'infinite' then
54 allowing an infinite amount of data to flow through the buffer.
198 in an infinite loop which does some action repeatedly. The safe430 patched. Otherwise, the code would end up in an infinite loop. A
162 supported by the graph traversal API. To prevent infinite loops, the graph
20 corresponding /dev/watchdogN device. A value of 0 means an infinite
224 - The lens is set to focus on an object at infinite distance.
366 0: means infinite timeout - no checking done.391 -1: report an infinite number of warnings.
74 between 0 and infinite time, until a wake-up event occurs.
183 assumes that the device driver has gone into an infinite loop
523 and allow infinite transmission time.
1863 avoid infinite Neighbor Solicitation "recursion" when the peer node
682 goes into an infinite loop (calling cond_sched() to let other tasks
445 in an infinite loop to prevent any speculative execution jumping to
581 typing - an infinite number of monkeys typing into GNU emacs would never
66 care of pinging a hardware watchdog. A value of 0 means infinite. The
419 set inf_bit, 0x1 # infinite result
