Searched full:situations (Results 1 – 25 of 796) sorted by relevance
12345678910>>...32
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | arrayRCU.rst | 7 also be used to protect arrays. Three situations are as follows:
15 Each of these three situations involves an RCU-protected pointer to an
26 That aside, each of the three RCU-protected pointer situations are
37 to other array-of-list situations, such as radix trees.
|
| /kernel/linux/linux-6.6/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
183 There are situations in which idle CPUs cannot be permitted to
261 of other situations where the scheduling-clock tick is not
278 Better handling of these sorts of situations is future work.
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | no_hz.rst | 38 there are some situations where this old-school approach is still the
80 unnecessary scheduling-clock interrupts. In these situations, there
121 by one less than the number of CPUs. In these situations, there is
183 There are situations in which idle CPUs cannot be permitted to
265 of other situations where the scheduling-clock tick is not
282 Better handling of these sorts of situations is future work.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/tools/memory-model/Documentation/ |
| D | access-marking.txt | 53 In fact, the following sections describe situations where use of
61 Here are some situations where data_race() should be used instead of
78 values are ignored, and other situations where reads from shared variables
166 Here are some example situations where plain C-language accesses should
173 wide variety of situations, including the uniprocessor phase of
176 data structures, and the cleanup side of any of these situations.
|
| /kernel/linux/linux-5.10/arch/powerpc/include/asm/nohash/32/ |
| D | pte-44x.h | 60 * certain situations. In other words, in such situations some portion of
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/lib/zlib_inflate/ |
| D | Makefile | 13 # any nasty situations wrt memory management, and that the
|
| /kernel/linux/linux-6.6/lib/zlib_inflate/ |
| D | Makefile | 13 # any nasty situations wrt memory management, and that the
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
223 be situations that call out for a different solution, and these guidelines
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-real_power_state | 17 In some situations the value of this attribute may be different
|
| D | sysfs-class-bdi | 46 situations where we want to avoid one device taking all or
|
| D | sysfs-bus-iio-trigger-sysfs | 9 automated testing or in situations, where other trigger methods
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
| D | qcom,usb-vbus-regulator.yaml | 14 regulator will be enabled in situations where the device is required to
|
| /kernel/linux/linux-6.6/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:
|
| /kernel/linux/linux-5.10/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:
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/ |
| D | qcom,usb-vbus-regulator.yaml | 14 regulator will be enabled in situations where the device is required to
|
| /kernel/linux/linux-5.10/Documentation/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/nvmem/ |
| D | qcom,sec-qfprom.yaml | 14 protected from non-secure access. In such situations, the OS have to use
|
12345678910>>...32