Searched full:situations (Results 1 – 25 of 440) sorted by relevance
12345678910>>...18
| /linux-6.12.1/Documentation/ABI/testing/ |
| 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
|
| D | sysfs-fs-erofs | 18 - 2 (force off): disable for all situations.
|
| D | sysfs-devices-real_power_state | 17 In some situations the value of this attribute may be different
|
| D | sysfs-bus-iio-trigger-sysfs | 9 automated testing or in situations, where other trigger methods
|
| /linux-6.12.1/Documentation/timers/ |
| 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-6.12.1/Documentation/locking/ |
| 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-6.12.1/drivers/iio/adc/ |
| D | ad7606_par.c | 33 * allows to recover from such failure situations. in ad7606_par16_read_block()
67 * allows to recover from such failure situations. in ad7606_par8_read_block()
|
| /linux-6.12.1/tools/memory-model/Documentation/ |
| 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-6.12.1/Documentation/maintainer/ |
| 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-6.12.1/drivers/gpu/drm/amd/display/dc/dml/dcn10/ |
| 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-6.12.1/lib/zlib_inflate/ |
| D | Makefile | 13 # any nasty situations wrt memory management, and that the
|
| /linux-6.12.1/Documentation/i2c/ |
| 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-6.12.1/Documentation/admin-guide/ |
| D | edid.rst | 24 As a remedy for such situations, the kernel configuration item
|
| /linux-6.12.1/Documentation/arch/arm/ |
| 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-6.12.1/Documentation/devicetree/bindings/nvmem/ |
| D | qcom,sec-qfprom.yaml | 14 protected from non-secure access. In such situations, the OS have to use
|
| /linux-6.12.1/Documentation/devicetree/bindings/regulator/ |
| D | qcom,usb-vbus-regulator.yaml | 14 regulator will be enabled in situations where the device is required to
|
| /linux-6.12.1/Documentation/networking/device_drivers/can/freescale/ |
| D | flexcan.rst | 25 performs better under high system load situations.
|
| /linux-6.12.1/drivers/usb/dwc3/ |
| D | Makefile | 37 # which is arch-specific and that it compiles on all situations.
|
| /linux-6.12.1/include/linux/ |
| D | coresight-pmu.h | 18 * in certain situations:-
|
| /linux-6.12.1/tools/include/linux/ |
| D | coresight-pmu.h | 18 * in certain situations:-
|
| /linux-6.12.1/drivers/gpu/drm/ |
| D | drm_vblank_work.c | 25 * there's a few situations where it can't be helped. Some unforgiving
31 * context. Both of these situations can't be solved perfectly in Linux since
|
| /linux-6.12.1/Documentation/mm/ |
| D | overcommit-accounting.rst | 23 use, in most situations this means a process will not be
|
| /linux-6.12.1/fs/bcachefs/ |
| D | thread_with_file.h | 26 * situations slightly exceed that limit so as to avoid chopping off a
|
| /linux-6.12.1/Documentation/core-api/ |
| D | kref.rst | 148 know what you are doing (there are some situations where locking is
153 There are some situations where you can optimize the gets and puts.
|
| /linux-6.12.1/arch/mips/include/asm/octeon/ |
| 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
|
12345678910>>...18