From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Liang, Kan" <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: Mon, 6 Feb 2023 11:51:44 -0300 [thread overview]
Message-ID: <Y+EUAEPhU8hVMLsl@kernel.org> (raw)
In-Reply-To: <47f5639d-a64e-9c85-a62b-40160d02d3ff@linux.intel.com>
Em Mon, Feb 06, 2023 at 09:32:00AM -0500, Liang, Kan escreveu:
>
>
> On 2023-02-03 3:28 p.m., Arnaldo Carvalho de Melo wrote:
> > Em Fri, Feb 03, 2023 at 05:21:15PM -0300, Arnaldo Carvalho de Melo escreveu:
> >> Em Thu, Feb 02, 2023 at 09:34:02AM -0500, Liang, Kan escreveu:
> >>> Hi Arnaldo,
> >>>
> >>> On 2023-02-01 8:47 p.m., Arnaldo Carvalho de Melo wrote:
> >>>> 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?
> >>> Yes, the kernel part has been merged into the tip.git perf/core branch.
> >>>
> >>> Thanks for checking the status. There are two perf tool patches in this
> >>> series, which hasn't been merged. Should I resend them?
> >>
> >> Lemme try cherry-picking just the tooling bits from this series.
> >
>
> Sorry, I forgot to mention it in this thread.
> I sent V3 with only perf tool patches.
>
> https://lore.kernel.org/lkml/20230202192209.1795329-1-kan.liang@linux.intel.com/
>
> > There was a clash with:
> >
> > commit 3fd7a168bf51497909dbfb7347af28b5c57e74a6
> > Author: Namhyung Kim <namhyung@kernel.org>
> > Date: Thu Jan 26 13:36:10 2023 -0800
> >
> > perf script: Add 'cgroup' field for output
> >
> > And a minor fuzz on the first patch, I applied manually and resolved the
> > conflict,
>
> The V3 add a perf test case for the new field. Could you please apply it
> as well?
>
> Sorry for the inconvenience.
np, I'll pick the test and apply it as well,
Thanks for letting me know,
- Arnaldo
next prev parent reply other threads:[~2023-02-06 14:51 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 ` [PATCH V2 7/9] " Arnaldo Carvalho de Melo
2023-02-02 14:34 ` 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 [this message]
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=Y+EUAEPhU8hVMLsl@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