From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Perry Taylor <perry.taylor@intel.com>,
Samantha Alt <samantha.alt@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>,
Weilin Wang <weilin.wang@intel.com>,
Edward Baker <edward.baker@intel.com>
Subject: Re: [PATCH v1 00/12] perf vendor events intel update
Date: Thu, 21 Mar 2024 12:23:43 -0300 [thread overview]
Message-ID: <ZfxQ_68hcyag2itr@x1> (raw)
In-Reply-To: <c1ade566-111a-46b2-81b7-c165890c84ce@linux.intel.com>
On Thu, Mar 21, 2024 at 11:14:35AM -0400, Liang, Kan wrote:
>
>
> On 2024-03-21 10:25 a.m., Arnaldo Carvalho de Melo wrote:
> > On Wed, Mar 20, 2024 at 11:00:04PM -0700, Ian Rogers wrote:
> >> Update events to the latest on:
> >> https://github.com/intel/perfmon
> >>
> >> Using the converter script:
> >> https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
> >
> > Kan,
> >
> > Can you please take a look and provide an Acked or Reviewed-by?
> >
>
>
> Sure. The patch series look good to me. Thanks Ian!
>
> Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Thanks!
- Arnaldo
prev parent reply other threads:[~2024-03-21 15:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 6:00 [PATCH v1 00/12] perf vendor events intel update Ian Rogers
2024-03-21 6:00 ` [PATCH v1 01/12] perf vendor events intel: Update cascadelakex to 1.21 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 02/12] perf vendor events intel: Update emeraldrapids to 1.06 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 03/12] perf vendor events intel: Update grandridge to 1.02 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 04/12] perf vendor events intel: Update icelakex to 1.24 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 05/12] perf vendor events intel: Update lunarlake to 1.01 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 06/12] perf vendor events intel: Update meteorlake to 1.08 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 07/12] perf vendor events intel: Update sapphirerapids to 1.20 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 08/12] perf vendor events intel: Update sierraforest to 1.02 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 09/12] perf vendor events intel: Update skylakex to 1.33 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 10/12] perf vendor events intel: Update skylake to v58 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 11/12] perf vendor events intel: Update snowridgex to 1.22 Ian Rogers
2024-03-21 6:00 ` [PATCH v1 12/12] perf vendor events intel: Remove info metrics erroneously in TopdownL1 Ian Rogers
2024-03-21 14:25 ` [PATCH v1 00/12] perf vendor events intel update Arnaldo Carvalho de Melo
2024-03-21 15:14 ` Liang, Kan
2024-03-21 15:23 ` 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=ZfxQ_68hcyag2itr@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=edward.baker@intel.com \
--cc=irogers@google.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=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@intel.com \
--cc=weilin.wang@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).