| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-bdi | 68 situations where we want to avoid one device taking all or
81 of 1 million. This is useful in situations where we want to avoid
109 situations where we want to avoid one device taking all or
122 is useful in situations where the global limit is much higher than
|
| H A D | sysfs-devices-real_power_state | 17 In some situations the value of this attribute may be different
|
| H A D | sysfs-fs-erofs | 18 - 2 (force off): disable for all situations.
|
| H A D | sysfs-bus-iio-trigger-sysfs | 9 automated testing or in situations, where other trigger methods
|
| /linux/Documentation/timers/ |
| H A D | no_hz.rst | 38 there are some situations where this old-school approach is still the
84 unnecessary scheduling-clock interrupts. In these situations, there
121 by one less than the number of CPUs. In these situations, there is
180 There are situations in which idle CPUs cannot be permitted to
258 of other situations where the scheduling-clock tick is not
275 Better handling of these sorts of situations is future work.
|
| /linux/Documentation/locking/ |
| H A D | preempt-locking.rst | 15 requires explicit additional locking for very few additional situations.
18 requires protecting these situations.
35 protect these situations by disabling preemption around them.
|
| /linux/tools/memory-model/Documentation/ |
| H A D | access-marking.txt | 59 In fact, the following sections describe situations where use of
67 Here are some situations where data_race() should be used instead of
84 values are ignored, and other situations where reads from shared variables
172 Here are some example situations where plain C-language accesses should
179 wide variety of situations, including the uniprocessor phase of
182 data structures, and the cleanup side of any of these situations.
|
| /linux/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 111 the mainline. The best practices to follow differ in those two situations.
190 as always, in such situations, the merge commit should explain why the
219 be situations that call out for a different solution, and these guidelines
|
| /linux/drivers/gpu/drm/amd/display/dc/dml/dcn10/ |
| H A D | dcn10_fpu.c | 53 * isolate FPU operations in a single place, we must avoid situations where
59 * situations where developers forgot to use the FP protection before calling
|
| /linux/lib/zlib_inflate/ |
| H A D | Makefile | 13 # any nasty situations wrt memory management, and that the
|
| /linux/Documentation/i2c/ |
| H A D | gpio-fault-injection.rst | 46 The following fault injectors create situations where SDA will be held low by a
47 device. Bus recovery should be able to fix these situations. But please note:
|
| /linux/Documentation/arch/arm/ |
| H A D | vlocks.rst | 10 which are otherwise non-coherent, in situations where the hardware
89 vlocks are therefore best suited to situations where it is necessary
|
| /linux/Documentation/admin-guide/ |
| H A D | edid.rst | 24 As a remedy for such situations, the kernel configuration item
|
| /linux/Documentation/devicetree/bindings/nvmem/ |
| H A D | qcom,sec-qfprom.yaml | 14 protected from non-secure access. In such situations, the OS have to use
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | qcom,usb-vbus-regulator.yaml | 14 regulator will be enabled in situations where the device is required to
|
| /linux/drivers/iio/adc/ |
| H A D | ad7606_par.c | 119 * allows to recover from such failure situations. in ad7606_par16_read_block()
153 * allows to recover from such failure situations. in ad7606_par8_read_block()
|
| /linux/Documentation/networking/device_drivers/can/freescale/ |
| H A D | flexcan.rst | 25 performs better under high system load situations.
|
| /linux/include/linux/ |
| H A D | coresight-pmu.h | 18 * in certain situations:-
|
| /linux/tools/include/linux/ |
| H A D | coresight-pmu.h | 18 * in certain situations:-
|
| /linux/arch/mips/include/asm/octeon/ |
| H A D | cvmx-bootmem.h | 324 * Locks the bootmem allocator. This is useful in certain situations
332 * Unlocks the bootmem allocator. This is useful in certain situations
|
| /linux/Documentation/mm/ |
| H A D | overcommit-accounting.rst | 23 use, in most situations this means a process will not be
|
| H A D | unevictable-lru.rst | 191 from the unevictable list. However, there may be situations where we decide,
198 There may be situations where a folio is mapped into a VM_LOCKED VMA,
217 SYSV SHM. Note that mlock() is only available in CONFIG_MMU=y situations; in
218 NOMMU situations, all mappings are effectively mlocked.
|
| /linux/block/ |
| H A D | badblocks.c | 31 * It is difficult and unnecessary to take care of all the possible situations,
39 * When setting a range of bad blocks to the bad table, the simplified situations
137 * situations in 2).
206 * handled as the situations 4.1), the rest range S2 will be handled in next
319 * All the above 5 simplified situations and 3 special cases may cover 99%+ of
339 * bad block table. The simplified situations to be considered are, (The already
351 * For the above situations, no bad block to be cleared and no failure
446 * All bad blocks range clearing can be simplified into the above 5 situations
1106 * Both situations are to clear non-bad range, in _badblocks_clear()
|
| /linux/Documentation/driver-api/iio/ |
| H A D | triggers.rst | 12 In many situations it is useful for a driver to be able to capture data based
|
| /linux/Documentation/admin-guide/mm/damon/ |
| H A D | lru_sort.rst | 20 situations including reclamation target pages selection under sudden memory
44 be widely used without harm for common situations while providing a level of
|