From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Xing Zhengjun <zhengjun.xing@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
John Garry <john.garry@huawei.com>,
James Clark <james.clark@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/7] perf vendor events intel: Update CLX events to v1.15
Date: Wed, 4 May 2022 12:53:54 -0300 [thread overview]
Message-ID: <YnKhkv+BVT47Hph7@kernel.org> (raw)
In-Reply-To: <YnKgvLxcRhu6i53j@kernel.org>
Em Wed, May 04, 2022 at 12:50:20PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, May 03, 2022 at 12:47:25PM -0700, Ian Rogers escreveu:
> > On Thu, Apr 28, 2022 at 6:31 AM Arnaldo Carvalho de Melo
> > <acme@kernel.org> wrote:
> > >
> > > Em Thu, Apr 28, 2022 at 09:12:26AM -0400, Liang, Kan escreveu:
> > > >
> > > >
> > > > On 4/28/2022 3:57 AM, Ian Rogers wrote:
> > > > > Events are generated for CascadeLake Server v1.15 with
> > > > > events from:
> > > > > https://download.01.org/perfmon/CLX/
> > > > >
> > > > > Using the scripts at:
> > > > > https://github.com/intel/event-converter-for-linux-perf/
> > > > >
> > > > > This change updates descriptions, adds INST_DECODED.DECODERS and
> > > > > corrects a counter mask in UOPS_RETIRED.TOTAL_CYCLES.
> > > > >
> > > > > Signed-off-by: Ian Rogers<irogers@google.com>
> > > >
> > > > Thanks Ian. For the whole series,
> > > >
> > > > Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
> > >
> > > Thanks, applied.
> > >
> > > - Arnaldo
> >
> > Thanks Arnaldo, it looks like CLX was accidentally skipped.
>
> Checking, I usually take these using b4...
Got it now, checked the other 6 patches are in.
Thanks for pointing this out.
- Arnaldo
prev parent reply other threads:[~2022-05-04 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220428075730.797727-1-irogers@google.com>
2022-04-28 7:57 ` [PATCH 2/7] perf vendor events intel: Update ICL events to v1.13 Ian Rogers
2022-04-28 7:57 ` [PATCH 3/7] perf vendor events intel: Update IVT events to v21 Ian Rogers
2022-04-28 7:57 ` [PATCH 5/7] perf vendor events intel: Update SKX events to v1.27 Ian Rogers
2022-04-28 7:57 ` [PATCH 6/7] perf vendor events intel: Update WSM-EP-SP events to v3 Ian Rogers
2022-04-28 7:57 ` [PATCH 7/7] perf vendor events intel: Update WSM-EX " Ian Rogers
2022-04-28 13:12 ` [PATCH 1/7] perf vendor events intel: Update CLX events to v1.15 Liang, Kan
2022-04-28 13:31 ` Arnaldo Carvalho de Melo
2022-05-03 19:47 ` Ian Rogers
2022-05-04 15:50 ` Arnaldo Carvalho de Melo
2022-05-04 15:53 ` Arnaldo Carvalho de Melo [this message]
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=YnKhkv+BVT47Hph7@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=zhengjun.xing@linux.intel.com \
/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).