From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
x86@kernel.org, Dave Hansen <dave.hansen@linux.intel.com>,
Tony Luck <tony.luck@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, "H . Peter Anvin" <hpa@zytor.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Zhang Rui <rui.zhang@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
David Laight <david.laight.linux@gmail.com>,
Dapeng Mi <dapeng1.mi@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 14/15] perf/x86: Simplify Intel PMU initialization
Date: Wed, 19 Feb 2025 15:10:42 -0500 [thread overview]
Message-ID: <49c59a81-015f-46a1-88b9-f043ca2710d0@linux.intel.com> (raw)
In-Reply-To: <20250219184133.816753-15-sohil.mehta@intel.com>
On 2025-02-19 1:41 p.m., Sohil Mehta wrote:
> Architectural Perfmon was introduced on the Family 6 "Core" processors
> starting with Yonah. Processors before Yonah need their own customized
> PMU initialization.
>
> p6_pmu_init() is expected to provide that initialization for early
> Family 6 processors. But, due to the unrestricted call to p6_pmu_init(),
> it could get called for any Family 6 processor if the architectural
> perfmon feature is disabled on that processor.
>
> To simplify, restrict the call to p6_pmu_init() to early Family 6
> processors that do not have architectural perfmon support. As a result,
> the "unsupported" console print becomes practically unreachable because
> all the released P6 processors are covered by the switch cases.
>
> Move the console print to a common location where it can cover all
> modern processors that do not have architectural perfmon support.
>
> Also, use this opportunity to get rid of the unnecessary switch cases in
> p6_pmu_init(). Only the Pentium Pro processor needs a quirk, and the
> rest of the processors do not need any special handling. The gaps in the
> case numbers are only due to no processor with those model numbers being
> released.
>
> Converting to a VFM based check gets rid of one last few Intel x86_model
> comparisons.
>
> Signed-off-by: Sohil Mehta <sohil.mehta@intel.com>
> ---
> v3: Restrict calling p6_pmu_init() to only when needed.
> Move the console print to a common location.
>
> v2: No change.
> ---
> arch/x86/events/intel/core.c | 16 +++++++++++-----
> arch/x86/events/intel/p6.c | 26 +++-----------------------
> 2 files changed, 14 insertions(+), 28 deletions(-)
>
> diff --git a/arch/x86/events/intel/core.c b/arch/x86/events/intel/core.c
> index 7601196d1d18..c645d8c8ab87 100644
> --- a/arch/x86/events/intel/core.c
> +++ b/arch/x86/events/intel/core.c
> @@ -6466,16 +6466,22 @@ __init int intel_pmu_init(void)
> char *name;
> struct x86_hybrid_pmu *pmu;
>
> + /* Architectural Perfmon was introduced starting with INTEL_CORE_YONAH */
> if (!cpu_has(&boot_cpu_data, X86_FEATURE_ARCH_PERFMON)) {
> switch (boot_cpu_data.x86) {
> - case 0x6:
> - return p6_pmu_init();
> - case 0xb:
> + case 6:
> + if (boot_cpu_data.x86_vfm < INTEL_CORE_YONAH)
> + return p6_pmu_init();
> + break;
We may need a return -ENODEV here.
I think it's possible that some weird hypervisor doesn't enumerate the
ARCH_PERFMON for a modern CPU. Perf should not touch the leaf 10 if the
ARCH_PERFMON is not supported.
Thanks,
Kan
> + case 11:
> return knc_pmu_init();
> - case 0xf:
> + case 15:
> return p4_pmu_init();
> + default:
> + pr_cont("unsupported CPU family %d model %d ",
> + boot_cpu_data.x86, boot_cpu_data.x86_model);
> + return -ENODEV;
> }
> - return -ENODEV;
> }
>
> /*
> diff --git a/arch/x86/events/intel/p6.c b/arch/x86/events/intel/p6.c
> index a6cffb4f4ef5..65b45e9d7016 100644
> --- a/arch/x86/events/intel/p6.c
> +++ b/arch/x86/events/intel/p6.c
> @@ -2,6 +2,8 @@
> #include <linux/perf_event.h>
> #include <linux/types.h>
>
> +#include <asm/cpu_device_id.h>
> +
> #include "../perf_event.h"
>
> /*
> @@ -248,30 +250,8 @@ __init int p6_pmu_init(void)
> {
> x86_pmu = p6_pmu;
>
> - switch (boot_cpu_data.x86_model) {
> - case 1: /* Pentium Pro */
> + if (boot_cpu_data.x86_vfm == INTEL_PENTIUM_PRO)
> x86_add_quirk(p6_pmu_rdpmc_quirk);
> - break;
> -
> - case 3: /* Pentium II - Klamath */
> - case 5: /* Pentium II - Deschutes */
> - case 6: /* Pentium II - Mendocino */
> - break;
> -
> - case 7: /* Pentium III - Katmai */
> - case 8: /* Pentium III - Coppermine */
> - case 10: /* Pentium III Xeon */
> - case 11: /* Pentium III - Tualatin */
> - break;
> -
> - case 9: /* Pentium M - Banias */
> - case 13: /* Pentium M - Dothan */
> - break;
> -
> - default:
> - pr_cont("unsupported p6 CPU model %d ", boot_cpu_data.x86_model);
> - return -ENODEV;
> - }
>
> memcpy(hw_cache_event_ids, p6_hw_cache_event_ids,
> sizeof(hw_cache_event_ids));
next prev parent reply other threads:[~2025-02-19 20:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 18:41 [PATCH v3 00/15] Prepare for new Intel Family numbers Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 01/15] x86/apic: Fix 32-bit APIC initialization for extended Intel Families Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 02/15] x86/cpu/intel: Fix the movsl alignment preference for extended Families Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 03/15] x86/microcode: Update the Intel processor flag scan check Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 04/15] x86/mtrr: Modify a x86_model check to an Intel VFM check Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 05/15] x86/cpu/intel: Replace early Family 6 checks with VFM ones Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 06/15] x86/cpu/intel: Replace Family 15 " Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 07/15] x86/cpu/intel: Replace Family 5 model " Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 08/15] x86/acpi/cstate: Improve Intel Family model checks Sohil Mehta
2025-02-20 19:20 ` Rafael J. Wysocki
2025-02-19 18:41 ` [PATCH v3 09/15] x86/smpboot: Remove confusing quirk usage in INIT delay Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 10/15] x86/smpboot: Fix INIT delay assignment for extended Intel Families Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 11/15] x86/cpu/intel: Fix fast string initialization for extended Families Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 12/15] x86/pat: Replace Intel x86_model checks with VFM ones Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 13/15] x86/cpu/intel: Bound the non-architectural constant_tsc model checks Sohil Mehta
2025-08-21 13:15 ` David Woodhouse
2025-08-21 19:34 ` Sohil Mehta
2025-08-21 19:43 ` Sohil Mehta
2025-08-21 20:09 ` David Woodhouse
2025-08-22 1:46 ` Xiaoyao Li
2025-08-24 22:39 ` Demi Marie Obenour
2025-02-19 18:41 ` [PATCH v3 14/15] perf/x86: Simplify Intel PMU initialization Sohil Mehta
2025-02-19 20:10 ` Liang, Kan [this message]
2025-02-19 20:31 ` Sohil Mehta
2025-02-19 20:45 ` Liang, Kan
2025-02-27 0:16 ` [PATCH v3.1 " Sohil Mehta
2025-02-19 18:41 ` [PATCH v3 15/15] perf/x86/p4: Replace Pentium 4 model checks with VFM ones Sohil Mehta
2025-02-19 20:11 ` Liang, Kan
2025-03-17 17:09 ` [PATCH v3 00/15] Prepare for new Intel Family numbers Sohil Mehta
2025-03-18 18:35 ` Ingo Molnar
2025-03-18 19:10 ` Sohil Mehta
2025-03-18 20:13 ` Ingo Molnar
2025-03-19 15:53 ` Sohil Mehta
2025-03-19 19:46 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49c59a81-015f-46a1-88b9-f043ca2710d0@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dapeng1.mi@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david.laight.linux@gmail.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=jdelvare@suse.com \
--cc=jolsa@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=viresh.kumar@linaro.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).