| /openbmc/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-fs-erofs | 18 - 2 (force off): disable for all situations.
|
| H A D | sysfs-devices-real_power_state | 17 In some situations the value of this attribute may be different
|
| /openbmc/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
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.
|
| /openbmc/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.
|
| /openbmc/docs/designs/ |
| H A D | power-recovery.md | 21 reset to the BMC in situations where it is hung or not responding. In these
22 situations, the user may wish for the system to not automatically power on the
72 These options are only checked and enforced in situations where the BMC does not
87 In situations where the BMC or the system have gotten into a bad state, and the
126 - Power system off as quickly as situations requires (or gracefully handle the
|
| H A D | target-fail-monitoring.md | 20 There are situations where OpenBMC systemd targets fail. They fail due to a
23 but in some situations (segfault, unhandled exception, unhandled error path,
173 fails. This will be viewable by owners of the system. There may be situations
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A 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.
|
| /openbmc/linux/drivers/iio/adc/ |
| H A 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()
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gnome/tracker/tinysparql/ |
| H A D | 0001-fix-reproducibility.patch | 55 # Global build root is required to detect noinst situations (tests/introspection),
85 # Global build root is required to detect noinst situations (tests/introspection),
|
| /openbmc/qemu/tests/keys/ |
| H A D | README | 6 ONLY in situations that cannot be compromised by external network clients.
|
| /openbmc/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
|
| /openbmc/linux/lib/zlib_inflate/ |
| H A D | Makefile | 13 # any nasty situations wrt memory management, and that the
|
| /openbmc/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
|
| /openbmc/u-boot/doc/device-tree-bindings/net/ |
| H A D | fixed-link.txt | 5 normal MDIO-managed PHY device. For those situations, a Device Tree
|
| /openbmc/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:
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/p910nd/ |
| H A D | p910nd_0.97.bb | 1 DESCRIPTION = "A small network printer daemon for embedded situations that passes the job directly …
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
| H A D | SBE.interface.yaml | 8 unresponsive. In such situations, the debug data needs to be collected from
|
| /openbmc/openbmc/poky/meta/recipes-kernel/linux/ |
| H A D | linux-dummy.bb | 3 provider for virtual/kernel to satisfy dependencies for situations \
|
| /openbmc/u-boot/doc/ |
| H A D | README.displaying-bmps | 6 make sure all data is properly aligned, and in many situations simply choosing
|
| /openbmc/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
|
| /openbmc/openbmc/meta-phosphor/recipes-core/systemd/phosphor-systemd-policy/ |
| H A D | service-restart-policy.conf | 19 # it's even more challenged. Recent failures have shown situations where
|
| /openbmc/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
|
| /openbmc/qemu/docs/user/ |
| H A D | main.rst | 95 This slows down emulation a lot, but can be useful in some situations,
238 This slows down emulation a lot, but can be useful in some situations,
|
| /openbmc/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
|