Searched refs:infinite (Results 1 – 23 of 23) sorted by relevance
| /Linux-v5.10/drivers/mtd/tests/ |
| D | torturetest.c | 171 int err = 0, i, infinite = !cycles_count; in tort_init() local
332 if (!infinite && --cycles_count == 0) in tort_init()
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-class-uwb_rc-wusbhc | 57 valid values is [0..15], where 0 indicates infinite retries.
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | directory-locking.rst | 110 Otherwise the set of contended objects would be infinite - each of them
117 would again have an infinite set of contended objects). But that
|
| D | fuse.rst | 99 The default is infinite. Note that the size of read requests is
|
| /Linux-v5.10/arch/openrisc/ |
| D | Kconfig | 181 Now this puts kernel into infinite loop after first oops. Till
|
| /Linux-v5.10/Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 87 to complete before exiting. Note that if 'iterations' is set to 'infinite' then
|
| /Linux-v5.10/Documentation/core-api/ |
| D | circular-buffers.rst | 54 allowing an infinite amount of data to flow through the buffer.
|
| /Linux-v5.10/Documentation/livepatch/ |
| D | livepatch.rst | 198 in an infinite loop which does some action repeatedly. The safe
430 patched. Otherwise, the code would end up in an infinite loop. A
|
| /Linux-v5.10/Documentation/driver-api/driver-model/ |
| D | driver.rst | 183 device has been registered, it may result in an infinite loop of
|
| /Linux-v5.10/Documentation/driver-api/media/ |
| D | mc-core.rst | 162 supported by the graph traversal API. To prevent infinite loops, the graph
|
| /Linux-v5.10/Documentation/watchdog/ |
| D | watchdog-parameters.rst | 20 corresponding /dev/watchdogN device. A value of 0 means an infinite
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-camera.rst | 217 - The lens is set to focus on an object at infinite distance.
|
| /Linux-v5.10/Documentation/networking/device_drivers/hamradio/ |
| D | z8530drv.rst | 544 and allow infinite transmission time.
|
| /Linux-v5.10/Documentation/PCI/ |
| D | pci-error-recovery.rst | 183 assumes that the device driver has gone into an infinite loop
|
| /Linux-v5.10/Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 379 0 means infinite timeout, no checking is done.
406 -1: report an infinite number of warnings.
|
| /Linux-v5.10/kernel/trace/ |
| D | Kconfig | 661 goes into an infinite loop (calling cond_sched() to let other tasks
|
| /Linux-v5.10/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 445 in an infinite loop to prevent any speculative execution jumping to
|
| /Linux-v5.10/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 985 | In theory, an infinite number. In practice, an unknown number that is |
1420 example, an infinite loop in an RCU read-side critical section must by
1628 #. An infinite loop in an RCU read-side critical section will eventually
|
| /Linux-v5.10/Documentation/process/ |
| D | coding-style.rst | 606 typing - an infinite number of monkeys typing into GNU emacs would never
|
| /Linux-v5.10/tools/memory-model/Documentation/ |
| D | litmus-tests.txt | 499 Potentially infinite loops, such as those used to wait for locks to
|
| /Linux-v5.10/drivers/watchdog/ |
| D | Kconfig | 66 care of pinging a hardware watchdog. A value of 0 means infinite. The
|
| /Linux-v5.10/Documentation/networking/ |
| D | ip-sysctl.rst | 2147 avoid infinite Neighbor Solicitation "recursion" when the peer node
|
| /Linux-v5.10/arch/m68k/ifpsp060/src/ |
| D | fplsp.S | 419 set inf_bit, 0x1 # infinite result
|
