| /Linux-v5.15/arch/arm/mm/ |
| D | proc-sa110.S | 95 mov r0, r0 @ safety
96 mov r0, r0 @ safety
97 mov r0, r0 @ safety
99 mov r0, r0 @ safety
100 mov r0, r0 @ safety
101 mov r0, r0 @ safety
|
| D | proc-sa1100.S | 111 mov r0, r0 @ safety
|
| /Linux-v5.15/arch/x86/include/asm/ |
| D | suspend_32.h | 29 unsigned long safety; member
|
| D | suspend_64.h | 49 unsigned long safety; member
|
| /Linux-v5.15/arch/powerpc/boot/dts/ |
| D | ac14xx.dts | 45 0x5 0x0 0xe0400000 0x00010000 /* CS5: safety */
125 safety@5,0 {
126 compatible = "ifm,safety";
|
| /Linux-v5.15/drivers/thermal/intel/int340x_thermal/ |
| D | Kconfig | 17 CPU/SOC, for thermal safety reasons.
|
| /Linux-v5.15/net/hsr/ |
| D | Kconfig | 38 relying on this code in a safety critical system!
|
| /Linux-v5.15/drivers/media/pci/saa7164/ |
| D | saa7164-cmd.c | 337 int safety = 0; in saa7164_cmd_send() local
445 if (safety++ > 16) { in saa7164_cmd_send()
|
| /Linux-v5.15/lib/ |
| D | Kconfig.kfence | 7 bool "KFENCE: low-overhead sampling-based memory safety error detector"
|
| /Linux-v5.15/Documentation/driver-api/driver-model/ |
| D | bus.rst | 53 type-safety.
|
| D | driver.rst | 49 sacrifice type-safety, so we keep bus-specific structures around.
|
| D | porting.rst | 121 This allows the compiler to verify type-safety of the operations
|
| /Linux-v5.15/arch/arm/boot/dts/ |
| D | arm-realview-eb-mp.dtsi | 74 * up by boot loader(s), probably for safety
|
| D | arm-realview-pb11mp.dts | 107 * up by boot loader(s), probably for safety
|
| /Linux-v5.15/drivers/net/wan/ |
| D | farsync.c | 911 int safety; in fst_issue_cmd() local
917 safety = 0; in fst_issue_cmd()
924 if (++safety > 2000) { in fst_issue_cmd()
931 if (safety > 0) in fst_issue_cmd()
932 dbg(DBG_CMD, "Mailbox clear after %d jiffies\n", safety); in fst_issue_cmd()
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | ocfs2.rst | 83 will hurt performance, but it's good for data-safety.
|
| /Linux-v5.15/Documentation/i2c/busses/ |
| D | i2c-parport.rst | 94 the i2c-parport module might be a good safety since data line state
|
| /Linux-v5.15/Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 582 wake up caused by the firmware will have negated most safety nets...
672 CAP_SYS_ADMIN capability for safety reasons, as it can interact badly
1210 safety reasons. To enable them, the module parameter "fan_control=1"
1269 120 seconds. This functionality is called fan safety watchdog.
1311 To program the safety watchdog, use the "watchdog" command::
1321 part, and the exception is the fan safety watchdog.
1361 Fan safety watchdog timer interval, in seconds. Minimum is
|
| /Linux-v5.15/Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 83 Without the option META\_BG, for safety concerns, all block group
|
| /Linux-v5.15/Documentation/trace/ |
| D | kprobes.rst | 190 Before optimizing a probe, Kprobes performs the following safety checks:
247 rather, it calls synchronize_rcu() for safety first, because it's
274 .. [4] This optimization-safety checking may be replaced with the
|
| /Linux-v5.15/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-gru-scarlet.dtsi | 37 * rounding up to 1ms for safety.
|
| /Linux-v5.15/Documentation/dev-tools/ |
| D | kfence.rst | 7 Kernel Electric-Fence (KFENCE) is a low-overhead sampling-based memory safety
|
| /Linux-v5.15/arch/arm64/boot/dts/qcom/ |
| D | msm8994-msft-lumia-octagon.dtsi | 863 * Set the speed to HS200 as a safety measure.
|
| /Linux-v5.15/Documentation/process/ |
| D | botching-up-ioctls.rst | 119 still too tricky have a timeout or hangcheck safety net as a last-ditch
|
| /Linux-v5.15/Documentation/networking/ |
| D | filter.rst | 884 is deterministic and the kernel can easily prove that. The safety of the program
1111 The safety of the eBPF program is determined in two steps.
1205 from safety point of view. The verifier will guarantee that the function is
1217 In order to determine the safety of an eBPF program, the verifier must track
|
