Searched full:situations (Results 1 – 25 of 360) sorted by relevance
12345678910>>...15
| /Linux-v5.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.
|
| /Linux-v5.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.
|
| /Linux-v5.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.
|
| /Linux-v5.10/arch/powerpc/include/asm/nohash/32/ |
| D | pte-44x.h | 60 * certain situations. In other words, in such situations some portion of
|
| /Linux-v5.10/lib/zlib_inflate/ |
| D | Makefile | 13 # any nasty situations wrt memory management, and that the
|
| /Linux-v5.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
|
| /Linux-v5.10/Documentation/devicetree/bindings/regulator/ |
| D | qcom,usb-vbus-regulator.yaml | 14 regulator will be enabled in situations where the device is required to
|
| /Linux-v5.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
|
| /Linux-v5.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:
|
| /Linux-v5.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
|
| /Linux-v5.10/Documentation/devicetree/bindings/watchdog/ |
| D | aspeed-wdt.txt | 20 This is useful in situations where another watchdog engine on chip is
|
| /Linux-v5.10/drivers/usb/dwc3/ |
| D | Makefile | 37 # which is arch-specific and that it compiles on all situations.
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | edid.rst | 24 As a remedy for such situations, the kernel configuration item
|
| D | cpu-load.rst | 51 One can imagine many more situations where this behavior of the kernel
|
| /Linux-v5.10/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-v5.10/arch/arm/mach-mstar/ |
| D | mstarv7.c | 44 * This may need locking to deal with situations where an interrupt
|
| /Linux-v5.10/Documentation/vm/ |
| D | overcommit-accounting.rst | 26 use, in most situations this means a process will not be
|
| /Linux-v5.10/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
|
| /Linux-v5.10/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-v5.10/Documentation/driver-api/iio/ |
| D | triggers.rst | 12 In many situations it is useful for a driver to be able to capture data based
|
| /Linux-v5.10/Documentation/power/ |
| D | pci.rst | 68 Thus in many situations both the native and the platform-based power management
231 may be identified later). The GPEs used in such situations are referred to as
302 These callbacks are executed by the PM core in various situations related to
407 situations. First, it may be called at the request of the device's driver, for
775 The freeze() callback is hibernation-specific and is executed in two situations,
920 The complete() callback is executed in the following situations:
1035 situations. If the PM core determines that the driver's "noirq" and "early"
1104 are a few situations in which power management requests are automatically
|
| /Linux-v5.10/Documentation/fb/ |
| D | tridentfb.rst | 59 detection says in all three BIOS selectable situations 2M, 4M, 8M.
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-subscribe-event.rst | 106 situations like that.
|
12345678910>>...15
