summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorAnthony Steinhauser <asteinhauser@google.com>2020-06-07 15:44:19 +0300
committerThomas Gleixner <tglx@linutronix.de>2020-06-09 11:50:55 +0300
commit4d8df8cbb9156b0a0ab3f802b80cb5db57acc0bf (patch)
tree0b12815b3168562c696e346601624c8c469a6711 /tools/perf/scripts/python/export-to-postgresql.py
parentdbbe2ad02e9df26e372f38cc3e70dab9222c832e (diff)
downloadlinux-4d8df8cbb9156b0a0ab3f802b80cb5db57acc0bf.tar.xz
x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
Currently, it is possible to enable indirect branch speculation even after it was force-disabled using the PR_SPEC_FORCE_DISABLE option. Moreover, the PR_GET_SPECULATION_CTRL command gives afterwards an incorrect result (force-disabled when it is in fact enabled). This also is inconsistent vs. STIBP and the documention which cleary states that PR_SPEC_FORCE_DISABLE cannot be undone. Fix this by actually enforcing force-disabled indirect branch speculation. PR_SPEC_ENABLE called after PR_SPEC_FORCE_DISABLE now fails with -EPERM as described in the documentation. Fixes: 9137bb27e60e ("x86/speculation: Add prctl() control for indirect branch speculation") Signed-off-by: Anthony Steinhauser <asteinhauser@google.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: stable@vger.kernel.org
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions