diff options
| author | Michael Ellerman <mpe@ellerman.id.au> | 2018-07-09 16:25:21 +1000 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2018-07-24 22:03:15 +1000 |
| commit | 6d44acae1937b81cf8115ada8958e04f601f3f2e (patch) | |
| tree | 340a4ddde4c8406d99c164649d96a9aaec4be555 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | powerpc: NMI IPI make NMI IPIs fully sychronous (diff) | |
| download | linux-6d44acae1937b81cf8115ada8958e04f601f3f2e.tar.gz linux-6d44acae1937b81cf8115ada8958e04f601f3f2e.zip | |
powerpc64s: Show ori31 availability in spectre_v1 sysfs file not v2
When I added the spectre_v2 information in sysfs, I included the
availability of the ori31 speculation barrier.
Although the ori31 barrier can be used to mitigate v2, it's primarily
intended as a spectre v1 mitigation. Spectre v2 is mitigated by
hardware changes.
So rework the sysfs files to show the ori31 information in the
spectre_v1 file, rather than v2.
Currently we display eg:
$ grep . spectre_v*
spectre_v1:Mitigation: __user pointer sanitization
spectre_v2:Mitigation: Indirect branch cache disabled, ori31 speculation barrier enabled
After:
$ grep . spectre_v*
spectre_v1:Mitigation: __user pointer sanitization, ori31 speculation barrier enabled
spectre_v2:Mitigation: Indirect branch cache disabled
Fixes: d6fbe1c55c55 ("powerpc/64s: Wire up cpu_show_spectre_v2()")
Cc: stable@vger.kernel.org # v4.17+
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions