diff options
| author | Michael Ellerman <mpe@ellerman.id.au> | 2020-04-02 23:49:29 +1100 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2020-05-18 21:58:43 +1000 |
| commit | d93e5e2d03d4f41dfedb92200a2c0413ab8ee4e7 (patch) | |
| tree | 8370a48a6588de9449b102a78c444ae99bc0e258 /Documentation/RCU | |
| parent | 93900337b9ac2f4eca427eff6d187be2dc3b5551 (diff) | |
powerpc/64: Update Speculation_Store_Bypass in /proc/<pid>/status
Currently we don't report anything useful in /proc/<pid>/status:
$ grep Speculation_Store_Bypass /proc/self/status
Speculation_Store_Bypass: unknown
Our mitigation is currently always a barrier instruction, which
doesn't map that well onto the existing possibilities for the PR_SPEC
values.
However even if we added a "barrier" type PR_SPEC value, userspace
would still need to consult some other source to work out which type
of barrier to use. So reporting "vulnerable" seems sufficient, as
userspace can see that and then consult its source to determine what
barrier to use.
Signed-off-by: Gustavo Walbon <gwalbon@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20200402124929.3574166-1-mpe@ellerman.id.au
Diffstat (limited to 'Documentation/RCU')
0 files changed, 0 insertions, 0 deletions