/Linux-v5.15/Documentation/x86/x86_64/ |
D | machinecheck.rst | 50 tolerant 57 deadlock. Higher tolerant values trade potentially better uptime 58 with the risk of a crash or even corruption (for tolerant >= 3).
|
/Linux-v5.15/arch/x86/kernel/cpu/mce/ |
D | core.c | 90 * Tolerant levels: 96 .tolerant = 1, 811 m.severity = mce_severity(&m, NULL, mca_cfg.tolerant, NULL, false); in machine_check_poll() 863 if (mce_severity(m, regs, mca_cfg.tolerant, &tmp, true) >= MCE_PANIC_SEVERITY) { in mce_no_way_out() 906 if (mca_cfg.tolerant <= 1) { in mce_timed_out() 971 if (m && global_worst >= MCE_PANIC_SEVERITY && mca_cfg.tolerant < 3) { in mce_reign() 973 mce_severity(m, NULL, mca_cfg.tolerant, &msg, true); in mce_reign() 987 if (global_worst <= MCE_KEEP_SEVERITY && mca_cfg.tolerant < 3) in mce_reign() 1221 severity = mce_severity(m, regs, cfg->tolerant, NULL, true); in __mc_scan_banks() 1364 * MCE. If mca_cfg.tolerant is cranked up, we'll try anyway. in do_machine_check() [all …]
|
D | severity.c | 320 static int mce_severity_amd(struct mce *m, struct pt_regs *regs, int tolerant, in mce_severity_amd() argument 374 int tolerant, char **msg, bool is_excp) in mce_severity_intel() argument 403 if (tolerant < 1) in mce_severity_intel() 411 int (*mce_severity)(struct mce *m, struct pt_regs *regs, int tolerant, char **msg, bool is_excp) =
|
D | internal.h | 42 int tolerant, char **msg, bool is_excp); 133 int tolerant; member
|
/Linux-v5.15/tools/memory-model/Documentation/ |
D | access-marking.txt | 69 3. Reads whose values feed into error-tolerant heuristics. 71 4. Writes setting values that feed into error-tolerant heuristics. 125 Reads Feeding Into Error-Tolerant Heuristics 146 Writes Setting Values Feeding Into Error-Tolerant Heuristics 148 The values read into error-tolerant heuristics come from somewhere,
|
/Linux-v5.15/arch/powerpc/mm/ptdump/ |
D | book3s64.c | 71 .set = "tolerant",
|
/Linux-v5.15/drivers/gpu/drm/i915/ |
D | i915_mitigations.c | 46 /* Be tolerant of leading/trailing whitespace */ in mitigations_set()
|
/Linux-v5.15/Documentation/devicetree/bindings/i3c/ |
D | i3c.yaml | 94 not tolerant to high frequencies
|
/Linux-v5.15/Documentation/vm/ |
D | hwpoison.rst | 63 (on x86 this can be also affected by the tolerant level of the
|
/Linux-v5.15/Documentation/filesystems/ |
D | ubifs.rst | 65 Similarly to JFFS2, UBIFS is tolerant of unclean reboots and power-cuts.
|
D | fiemap.rst | 204 structure directly. Filesystem handlers should be tolerant to signals and return
|
D | ntfs.rst | 271 For NT4 fault tolerant volumes you can obtain the sizes using fdisk. So for
|
/Linux-v5.15/Documentation/gpu/ |
D | vgaarbiter.rst | 85 a bit, but makes the arbiter more tolerant to user space problems and able
|
/Linux-v5.15/drivers/phy/intel/ |
D | phy-intel-lgm-emmc.c | 99 * failure cases are found which indicates we should be more tolerant in intel_emmc_phy_power()
|
D | phy-intel-keembay-emmc.c | 120 * failure cases are found which indicates we should be more tolerant in keembay_emmc_phy_power()
|
/Linux-v5.15/Documentation/admin-guide/ |
D | kernel-parameters.rst | 79 The special case-tolerant group name "all" has a meaning of selecting all CPUs,
|
/Linux-v5.15/drivers/phy/rockchip/ |
D | phy-rockchip-emmc.c | 174 * failure cases are found which indicates we should be more tolerant in rockchip_emmc_phy_power()
|
/Linux-v5.15/drivers/usb/serial/ |
D | cyberjack.c | 282 /* "+=" is probably more fault tolerant than "=" */ in cyberjack_read_int_callback()
|
D | ark3116.c | 680 * On my chip, all signals seem to be 3.3V, but 5V tolerant. But that
|
/Linux-v5.15/Documentation/powerpc/ |
D | eeh-pci-error-recovery.rst | 319 Ext3fs seems to be tolerant, retrying reads/writes until it does
|
/Linux-v5.15/net/ethernet/ |
D | eth.c | 194 * won't work for fault tolerant netware but does for the rest. in eth_type_trans()
|
/Linux-v5.15/Documentation/PCI/ |
D | pci-error-recovery.rst | 58 of the current Linux file systems are not tolerant of disconnection
|
/Linux-v5.15/include/linux/ |
D | if_vlan.h | 666 * 802.2 SSAP/DSAP. This won't work for fault tolerant netware in vlan_set_encap_proto()
|
/Linux-v5.15/drivers/gpu/drm/i915/display/ |
D | intel_dp_link_training.c | 539 * as 10 but for pre-DP 1.4 devices we set a very tolerant in intel_dp_link_training_clock_recovery()
|
/Linux-v5.15/drivers/gpu/drm/radeon/ |
D | r500_reg.h | 590 /* 78a8 appears to be some kind of (reasonably tolerant) clock?
|