aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/vm
diff options
context:
space:
mode:
authorBorislav Petkov <bp@suse.de>2021-12-20 21:43:28 +0100
committerBorislav Petkov <bp@suse.de>2022-02-23 11:09:25 +0100
commit7f1b8e0d6360178e3527d4f14e6921c254a86035 (patch)
tree21fd1faf6a1cbe36343dc8330da52c750bee7a33 /Documentation/vm
parentx86/mce: Work around an erratum on fast string copy instructions (diff)
downloadlinux-dev-7f1b8e0d6360178e3527d4f14e6921c254a86035.tar.xz
linux-dev-7f1b8e0d6360178e3527d4f14e6921c254a86035.zip
x86/mce: Remove the tolerance level control
This is pretty much unused and not really useful. What is more, all relevant MCA hardware has recoverable machine checks support so there's no real need to tweak MCA tolerance levels in order to *maybe* extend machine lifetime. So rip it out. Signed-off-by: Borislav Petkov <bp@suse.de> Link: https://lore.kernel.org/r/YcDq8PxvKtTENl/e@zn.tnic
Diffstat (limited to 'Documentation/vm')
-rw-r--r--Documentation/vm/hwpoison.rst2
1 files changed, 0 insertions, 2 deletions
diff --git a/Documentation/vm/hwpoison.rst b/Documentation/vm/hwpoison.rst
index 89b5f7a52077..c742de1769d1 100644
--- a/Documentation/vm/hwpoison.rst
+++ b/Documentation/vm/hwpoison.rst
@@ -60,8 +60,6 @@ There are two (actually three) modes memory failure recovery can be in:
vm.memory_failure_recovery sysctl set to zero:
All memory failures cause a panic. Do not attempt recovery.
- (on x86 this can be also affected by the tolerant level of the
- MCE subsystem)
early kill
(can be controlled globally and per process)