| /linux/drivers/mtd/tests/ |
| H A D | torturetest.c | 171 int err = 0, i, infinite = !cycles_count; in tort_init() local
330 if (!infinite && --cycles_count == 0) in tort_init()
|
| /linux/tools/sched_ext/ |
| H A D | README.md | 179 single CPU, allowing other cores to run with infinite slices, without timer
185 infinite slices and no timer ticks allows the VM to avoid unnecessary expensive
|
| /linux/tools/testing/selftests/ftrace/test.d/ |
| H A D | functions | 92 # Prevent infinite loops
|
| /linux/Documentation/scheduler/ |
| H A D | schedutil.rst | 26 Since this is essentially a progression of an infinite geometric series, the
|
| /linux/arch/openrisc/ |
| H A D | Kconfig | 249 Now this puts kernel into infinite loop after first oops. Till
|
| /linux/Documentation/core-api/ |
| H A D | circular-buffers.rst | 54 allowing an infinite amount of data to flow through the buffer.
|
| H A D | list.rst | 748 list_for_each() on ``stey`` results in an infinite loop, as it never returns
|
| /linux/Documentation/driver-api/dmaengine/ |
| H A D | dmatest.rst | 97 to complete before exiting. Note that if 'iterations' is set to 'infinite' then
|
| /linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 185 in an infinite loop which does some action repeatedly. The safe
417 patched. Otherwise, the code would end up in an infinite loop. A
|
| H A D | reliable-stacktrace.rst | 48 code, and should not get stuck in an infinite loop or access memory in
|
| /linux/Documentation/watchdog/ |
| H A D | watchdog-parameters.rst | 20 corresponding /dev/watchdogN device. A value of 0 means an infinite
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | driver.rst | 183 device has been registered, it may result in an infinite loop of
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-sched.txt | 496 repeat the workload n times (0: infinite). Default is 10.
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse.rst | 99 The default is infinite. Note that the size of read requests is
|
| /linux/kernel/trace/ |
| H A D | Kconfig | 811 functions are protected from kprobe-events to prevent an infinite
980 goes into an infinite loop (calling cond_resched() to let other tasks
|
| /linux/Documentation/networking/device_drivers/hamradio/ |
| H A D | z8530drv.rst | 544 and allow infinite transmission time.
|
| /linux/Documentation/PCI/ |
| H A D | pci-error-recovery.rst | 191 assumes that the device driver has gone into an infinite loop
|
| /linux/tools/memory-model/Documentation/ |
| H A D | ordering.txt | 226 used to prevent the compiler from moving code across an infinite loop:
|
| H A D | litmus-tests.txt | 499 Potentially infinite loops, such as those used to wait for locks to
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-camera.rst | 219 - The lens is set to focus on an object at infinite distance.
|
| /linux/scripts/ |
| H A D | spelling.txt | 863 infinit||infinite
|
| /linux/Documentation/admin-guide/sysctl/ |
| H A D | kernel.rst | 438 0 means infinite timeout, no checking is done.
465 -1: report an infinite number of warnings.
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | spectre.rst | 484 in an infinite loop to prevent any speculative execution jumping to
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 986 | In theory, an infinite number. In practice, an unknown number that is |
1421 example, an infinite loop in an RCU read-side critical section must by
1629 #. An infinite loop in an RCU read-side critical section will eventually
|
| /linux/Documentation/process/ |
| H A D | coding-style.rst | 648 typing - an infinite number of monkeys typing into GNU emacs would never
|