From: Dave Hansen <dave.hansen@intel.com>
To: Zhang Rui <rui.zhang@intel.com>, peterz@infradead.org
Cc: mingo@redhat.com, tglx@linutronix.de, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@linux.intel.com
Subject: Re: [PATCH 1/2] perf/x86/rapl: Add support for Intel Meteor Lake
Date: Wed, 4 Jan 2023 08:55:15 -0800 [thread overview]
Message-ID: <25d07838-3904-a086-4238-f56c9424b53a@intel.com> (raw)
In-Reply-To: <20230104145831.25498-1-rui.zhang@intel.com>
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?
next prev parent reply other threads:[~2023-01-04 16:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 14:58 [PATCH 1/2] perf/x86/rapl: Add support for Intel Meteor Lake Zhang Rui
2023-01-04 14:58 ` [PATCH 2/2] perf/x86/rapl: Add support for Intel Emerald Rapids Zhang Rui
2023-01-04 16:55 ` Dave Hansen [this message]
2023-01-05 6:54 ` [PATCH 1/2] perf/x86/rapl: Add support for Intel Meteor Lake Zhang, Rui
2023-01-05 9:55 ` Borislav Petkov
2023-01-06 6:05 ` Zhang, Rui
2023-01-06 10:14 ` Ingo Molnar
2023-01-06 10:39 ` Borislav Petkov
2023-01-06 10:56 ` Ingo Molnar
2023-01-06 11:11 ` Borislav Petkov
2023-01-06 11:33 ` Ingo Molnar
2023-01-06 14:45 ` Zhang, Rui
2023-01-06 14:38 ` Zhang, Rui
2023-01-06 14:49 ` Borislav Petkov
2023-01-06 14:50 ` Dave Hansen
2023-01-07 14:07 ` Zhang, Rui
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=25d07838-3904-a086-4238-f56c9424b53a@intel.com \
--to=dave.hansen@intel.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--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).