Searched full:situations (Results 1 – 25 of 680) sorted by relevance
12345678910>>...28
| /kernel/linux/linux-4.19/Documentation/RCU/ |
| D | arrayRCU.txt | 5 also be used to protect arrays. Three situations are as follows:
13 Each of these three situations involves an RCU-protected pointer to an
24 That aside, each of the three RCU-protected pointer situations are
33 to other array-of-list situations, such as radix trees.
|
| /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-4.19/Documentation/timers/ |
| D | NO_HZ.txt | 35 there are some situations where this old-school approach is still the
76 unnecessary scheduling-clock interrupts. In these situations, there
116 by one less than the number of CPUs. In these situations, there is
179 There are situations in which idle CPUs cannot be permitted to
259 of other situations where the scheduling-clock tick is not
276 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-4.19/Documentation/ |
| D | preempt-locking.txt | 16 requires explicit additional locking for very few additional situations.
19 requires protecting these situations.
36 protect these situations by disabling preemption around them.
|
| /kernel/linux/linux-4.19/Documentation/i2c/ |
| D | gpio-fault-injection | 42 The following fault injectors create situations where SDA will be held low by a
43 device. Bus recovery should be able to fix these situations. But please note:
|
| /kernel/linux/linux-4.19/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-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-4.19/lib/zlib_inflate/ |
| D | Makefile | 12 # any nasty situations wrt memory management, and that the
|
| /kernel/linux/linux-5.10/lib/zlib_inflate/ |
| D | Makefile | 13 # any nasty situations wrt memory management, and that the
|
| /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-4.19/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 | 47 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-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/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/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-4.19/Documentation/arm/ |
| D | vlocks.txt | 9 which are otherwise non-coherent, in situations where the hardware
88 vlocks are therefore best suited to situations where it is necessary
|
| /kernel/linux/linux-4.19/drivers/usb/dwc3/ |
| D | Makefile | 37 # which is arch-specific and that it compiles on all situations.
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/ |
| D | fixed-link.txt | 5 normal MDIO-managed PHY device. For those situations, a Device Tree
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/watchdog/ |
| D | aspeed-wdt.txt | 20 This is useful in situations where another watchdog engine on chip is
|
12345678910>>...28