aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Documentation/admin-guide/hw-vuln/mds.rst29
1 files changed, 13 insertions, 16 deletions
diff --git a/Documentation/admin-guide/hw-vuln/mds.rst b/Documentation/admin-guide/hw-vuln/mds.rst
index e0dccf414eca..e3a796c0d3a2 100644
--- a/Documentation/admin-guide/hw-vuln/mds.rst
+++ b/Documentation/admin-guide/hw-vuln/mds.rst
@@ -95,22 +95,19 @@ mitigations are active. The relevant sysfs file is:
95 95
96The possible values in this file are: 96The possible values in this file are:
97 97
98 ========================================= ================================= 98 .. list-table::
99 'Not affected' The processor is not vulnerable 99
100 100 * - 'Not affected'
101 'Vulnerable' The processor is vulnerable, 101 - The processor is not vulnerable
102 but no mitigation enabled 102 * - 'Vulnerable'
103 103 - The processor is vulnerable, but no mitigation enabled
104 'Vulnerable: Clear CPU buffers attempted' The processor is vulnerable but 104 * - 'Vulnerable: Clear CPU buffers attempted, no microcode'
105 microcode is not updated. 105 - The processor is vulnerable but microcode is not updated.
106 The mitigation is enabled on a 106
107 best effort basis. 107 The mitigation is enabled on a best effort basis. See :ref:`vmwerv`
108 See :ref:`vmwerv` 108 * - 'Mitigation: Clear CPU buffers'
109 109 - The processor is vulnerable and the CPU buffer clearing mitigation is
110 'Mitigation: CPU buffer clear' The processor is vulnerable and the 110 enabled.
111 CPU buffer clearing mitigation is
112 enabled.
113 ========================================= =================================
114 111
115If the processor is vulnerable then the following information is appended 112If the processor is vulnerable then the following information is appended
116to the above information: 113to the above information: