]>
Commit | Line | Data |
---|---|---|
b07c49f8 GKH |
1 | From 4a9ca3864343514ff4d6abc832b71566923c0b62 Mon Sep 17 00:00:00 2001 |
2 | From: Tyler Hicks <tyhicks@canonical.com> | |
3 | Date: Mon, 6 May 2019 23:52:58 +0000 | |
4 | Subject: [PATCH 26/27] Documentation: Correct the possible MDS sysfs values | |
5 | ||
6 | commit ea01668f9f43021b28b3f4d5ffad50106a1e1301 upstream | |
7 | ||
8 | Adjust the last two rows in the table that display possible values when | |
9 | MDS mitigation is enabled. They both were slightly innacurate. | |
10 | ||
11 | In addition, convert the table of possible values and their descriptions | |
12 | to a list-table. The simple table format uses the top border of equals | |
13 | signs to determine cell width which resulted in the first column being | |
14 | far too wide in comparison to the second column that contained the | |
15 | majority of the text. | |
16 | ||
17 | Signed-off-by: Tyler Hicks <tyhicks@canonical.com> | |
18 | Signed-off-by: Thomas Gleixner <tglx@linutronix.de> | |
19 | Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
20 | --- | |
21 | Documentation/admin-guide/hw-vuln/mds.rst | 29 ++++++++++------------- | |
22 | 1 file changed, 13 insertions(+), 16 deletions(-) | |
23 | ||
24 | diff --git a/Documentation/admin-guide/hw-vuln/mds.rst b/Documentation/admin-guide/hw-vuln/mds.rst | |
25 | index e0dccf414eca..e3a796c0d3a2 100644 | |
26 | --- a/Documentation/admin-guide/hw-vuln/mds.rst | |
27 | +++ b/Documentation/admin-guide/hw-vuln/mds.rst | |
28 | @@ -95,22 +95,19 @@ mitigations are active. The relevant sysfs file is: | |
29 | ||
30 | The possible values in this file are: | |
31 | ||
32 | - ========================================= ================================= | |
33 | - 'Not affected' The processor is not vulnerable | |
34 | - | |
35 | - 'Vulnerable' The processor is vulnerable, | |
36 | - but no mitigation enabled | |
37 | - | |
38 | - 'Vulnerable: Clear CPU buffers attempted' The processor is vulnerable but | |
39 | - microcode is not updated. | |
40 | - The mitigation is enabled on a | |
41 | - best effort basis. | |
42 | - See :ref:`vmwerv` | |
43 | - | |
44 | - 'Mitigation: CPU buffer clear' The processor is vulnerable and the | |
45 | - CPU buffer clearing mitigation is | |
46 | - enabled. | |
47 | - ========================================= ================================= | |
48 | + .. list-table:: | |
49 | + | |
50 | + * - 'Not affected' | |
51 | + - The processor is not vulnerable | |
52 | + * - 'Vulnerable' | |
53 | + - The processor is vulnerable, but no mitigation enabled | |
54 | + * - 'Vulnerable: Clear CPU buffers attempted, no microcode' | |
55 | + - The processor is vulnerable but microcode is not updated. | |
56 | + | |
57 | + The mitigation is enabled on a best effort basis. See :ref:`vmwerv` | |
58 | + * - 'Mitigation: Clear CPU buffers' | |
59 | + - The processor is vulnerable and the CPU buffer clearing mitigation is | |
60 | + enabled. | |
61 | ||
62 | If the processor is vulnerable then the following information is appended | |
63 | to the above information: | |
64 | -- | |
65 | 2.21.0 | |
66 |