[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25d07838-3904-a086-4238-f56c9424b53a@intel.com>
Date: Wed, 4 Jan 2023 08:55:15 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Zhang Rui <rui.zhang@...el.com>, peterz@...radead.org
Cc: mingo@...hat.com, tglx@...utronix.de, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
ak@...ux.intel.com, kan.liang@...ux.intel.com
Subject: Re: [PATCH 1/2] perf/x86/rapl: Add support for Intel Meteor Lake
On 1/4/23 06:58, Zhang Rui wrote:
> @@ -807,6 +807,8 @@ static const struct x86_cpu_id rapl_model_match[] __initconst = {
> X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE, &model_skl),
> X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P, &model_skl),
> X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_S, &model_skl),
> + X86_MATCH_INTEL_FAM6_MODEL(METEORLAKE, &model_skl),
> + X86_MATCH_INTEL_FAM6_MODEL(METEORLAKE_L, &model_skl),
> {},
> };
Any chance this will ever get architectural enumeration? Or, are we
doomed to grow this model list until the end of time?
Powered by blists - more mailing lists