diff options
| author | Breno Leitao <[email protected]> | 2024-10-01 14:10:19 +0000 |
|---|---|---|
| committer | Peter Zijlstra <[email protected]> | 2024-10-07 07:28:46 +0000 |
| commit | de20037e1b3c2f2ca97b8c12b8c7bca8abd509a7 (patch) | |
| tree | f3669d058f21ce06394935296ed16368bcb71fee /tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c | |
| parent | uprobes: fold xol_take_insn_slot() into xol_get_insn_slot() (diff) | |
| download | kernel-de20037e1b3c2f2ca97b8c12b8c7bca8abd509a7.tar.gz kernel-de20037e1b3c2f2ca97b8c12b8c7bca8abd509a7.zip | |
perf/x86/amd: Warn only on new bits set
Warning at every leaking bits can cause a flood of message, triggering
various stall-warning mechanisms to fire, including CSD locks, which
makes the machine to be unusable.
Track the bits that are being leaked, and only warn when a new bit is
set.
That said, this patch will help with the following issues:
1) It will tell us which bits are being set, so, it is easy to
communicate it back to vendor, and to do a root-cause analyzes.
2) It avoid the machine to be unusable, because, worst case
scenario, the user gets less than 60 WARNs (one per unhandled bit).
Suggested-by: Paul E. McKenney <[email protected]>
Signed-off-by: Breno Leitao <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Reviewed-by: Sandipan Das <[email protected]>
Reviewed-by: Paul E. McKenney <[email protected]>
Link: https://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c')
0 files changed, 0 insertions, 0 deletions