diff options
| author | Kan Liang <[email protected]> | 2023-01-12 12:01:05 -0800 |
|---|---|---|
| committer | Peter Zijlstra <[email protected]> | 2023-01-21 00:06:13 +0100 |
| commit | 5d515ee40cb57ea5331998f27df7946a69f14dc3 (patch) | |
| tree | 6267d3513cc417a8a2587c369e8b3c8b83fcbea5 /scripts/gdb/linux/config.py | |
| parent | 65248a9a9ee1ea2e6aad8f35253ffd9096ab81b7 (diff) | |
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] ------------[ cut here ]------------
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/x86/events/intel/uncore_discovery.c:184
intel_uncore_has_discovery_tables+0x4c0/0x65c
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.17-2136.313.1-X10-2c+ #4
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
Signed-off-by: Kan Liang <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Tested-by: Michael Petlan <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'scripts/gdb/linux/config.py')
0 files changed, 0 insertions, 0 deletions