perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
mainline inclusion from mainline-v6.3-rc1 commit 5d515ee4 category: bugfix bugzilla: https://gitee.com/openeuler/intel-kernel/issues/I7H29Y CVE: NA Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d515ee40cb57ea5331998f27df7946a69f14dc3 Intel-SIG: commit 5d515ee4 perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table Backport SPR MCC UPI uncore discovery warning fixes to OLK-5.10. ------------------------------------- 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: NKan Liang <kan.liang@linux.intel.com> Signed-off-by: NPeter Zijlstra (Intel) <peterz@infradead.org> Tested-by: NMichael Petlan <mpetlan@redhat.com> Link: https://lore.kernel.org/r/20230112200105.733466-6-kan.liang@linux.intel.comSigned-off-by: NYunying Sun <yunying.sun@intel.com>
Showing
想要评论请 注册 或 登录