From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: kan.liang@linux.intel.com
Cc: peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, ak@linux.intel.com,
eranian@google.com, irogers@google.com
Subject: Re: [PATCH V2 7/9] perf/x86/msr: Add Meteor Lake support
Date: Wed, 1 Feb 2023 22:47:14 -0300 [thread overview]
Message-ID: <Y9sWImm4v5I/MZId@kernel.org> (raw)
In-Reply-To: <20230104201349.1451191-7-kan.liang@linux.intel.com>
Em Wed, Jan 04, 2023 at 12:13:47PM -0800, kan.liang@linux.intel.com escreveu:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> Meteor Lake is Intel's successor to Raptor lake. PPERF and SMI_COUNT MSRs
> are also supported.
>
> Reviewed-by: Andi Kleen <ak@linux.intel.com>
> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
> ---
Did the kernel bits land upstream?
- Arnaldo
> No change since V1
>
> arch/x86/events/msr.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/x86/events/msr.c b/arch/x86/events/msr.c
> index ecced3a52668..074150d28fa8 100644
> --- a/arch/x86/events/msr.c
> +++ b/arch/x86/events/msr.c
> @@ -107,6 +107,8 @@ static bool test_intel(int idx, void *data)
> case INTEL_FAM6_RAPTORLAKE:
> case INTEL_FAM6_RAPTORLAKE_P:
> case INTEL_FAM6_RAPTORLAKE_S:
> + case INTEL_FAM6_METEORLAKE:
> + case INTEL_FAM6_METEORLAKE_L:
> if (idx == PERF_MSR_SMI || idx == PERF_MSR_PPERF)
> return true;
> break;
> --
> 2.35.1
--
- Arnaldo
next prev parent reply other threads:[~2023-02-02 1:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 20:13 [PATCH V2 1/9] perf: Add PMU_FORMAT_ATTR_SHOW kan.liang
2023-01-04 20:13 ` [PATCH V2 2/9] perf/x86: Add Meteor Lake support kan.liang
2023-01-09 17:02 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-01-04 20:13 ` [PATCH V2 3/9] perf/x86: Support Retire Latency kan.liang
2023-01-09 17:02 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-01-04 20:13 ` [PATCH V2 4/9] x86/cpufeatures: Add Architectural PerfMon Extension bit kan.liang
2023-01-09 17:02 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-01-04 20:13 ` [PATCH V2 5/9] perf/x86/intel: Support Architectural PerfMon Extension leaf kan.liang
2023-01-09 17:02 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-01-04 20:13 ` [PATCH V2 6/9] perf/x86/cstate: Add Meteor Lake support kan.liang
2023-01-09 11:15 ` [tip: perf/urgent] " tip-bot2 for Kan Liang
2023-01-09 17:02 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-01-04 20:13 ` [PATCH V2 7/9] perf/x86/msr: " kan.liang
2023-01-09 11:15 ` [tip: perf/urgent] " tip-bot2 for Kan Liang
2023-01-09 17:02 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-02-02 1:47 ` Arnaldo Carvalho de Melo [this message]
2023-02-02 14:34 ` [PATCH V2 7/9] " Liang, Kan
2023-02-02 14:45 ` Arnaldo Carvalho de Melo
2023-02-03 20:21 ` Arnaldo Carvalho de Melo
2023-02-03 20:28 ` Arnaldo Carvalho de Melo
2023-02-06 14:32 ` Liang, Kan
2023-02-06 14:51 ` Arnaldo Carvalho de Melo
2023-01-04 20:13 ` [PATCH V2 8/9] perf report: Support Retire Latency kan.liang
2023-01-04 20:13 ` [PATCH V2 9/9] perf script: " kan.liang
2023-01-09 17:02 ` [tip: perf/core] perf: Add PMU_FORMAT_ATTR_SHOW tip-bot2 for Kan Liang
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=Y9sWImm4v5I/MZId@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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