+41
−6
Loading
Merge Pull Request from: @yunyingsun Content: In mainline kernel before v6.11-rc1, PMU name for Intel next Xeon Granite Rapids(GNR) is the same as 4th and 5th gen Xeon(SPR and EMR). A new bugfix makes GNR using a different name for PMU. The fix patch is among a patch set of three which just landed mainline kernel v6.11-rc1: fa0c1c9d283b perf/x86/intel: Add a distinct name for Granite Rapids e5f32ad56b22 perf/x86/intel/ds: Fix non 0 retire latency on Raptorlake 556a7c039a52 perf/x86/intel: Hide Topdown metrics events if the feature is not enumerated This PR is to backport above fixes to kernel 5.10 for better GNR PMU support. Intel-kernel issue: https://gitee.com/openeuler/intel-kernel/issues/IAIG7E Test: Before backport on GNR, "dmesg | grep -i 'performance events'" shows "Sapphire Rapids events". After backport on GNR, "dmesg | grep -i 'performance events'" shows "Granite Rapids events". Known issue: N/A Configs: N/A Note: The backported patches were applied manually to kernel 5.10 with some adjustments, but no extra code changes comparing to upstream version. The backported patch set has been verified on Intel internal GNR. Link:https://gitee.com/openeuler/kernel/pulls/10799 Reviewed-by:Jason Zeng <jason.zeng@intel.com> Signed-off-by:
Yang Yingliang <yangyingliang@huawei.com>