From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com, irogers@google.com
Subject: Re: [PATCH 0/6] perf events update for CascadeLake server and SkyLake server
Date: Tue, 10 Aug 2021 15:07:22 -0300 [thread overview]
Message-ID: <YRLAWhHWX3oa0iyt@kernel.org> (raw)
In-Reply-To: <20210810020508.31261-1-yao.jin@linux.intel.com>
Em Tue, Aug 10, 2021 at 10:05:02AM +0800, Jin Yao escreveu:
> - Update JSON core/uncore events and metrics for CascadeLake Server.
> - Update JSON core/uncore events and metrics for SkyLake Server.
>
> The patch series can be found at (in case broken by mailing system potentially):
> https://github.com/yaoj/perf-clx-events.git
> branch: perf/core
Hey, can you keep just one repository and then create branches?
$ git remote -v
yaoj https://github.com/yaoj/icx-events.git (fetch)
yaoj https://github.com/yaoj/icx-events.git (push)
yaoj-perf https://github.com/yaoj/perf-intel-events.git (fetch)
yaoj-perf https://github.com/yaoj/perf-intel-events.git (push)
And now:
⬢[acme@toolbox perf]$ https://github.com/yaoj/perf-clx-events.git
:-)
Applying from the git tree now.
- Arnaldo
> Jin Yao (6):
> perf vendor events intel: Update core event list for CascadeLake
> Server
> perf vendor events intel: Update uncore event list for CascadeLake
> Server
> perf vendor events: Update metrics for CascadeLake Server
> perf vendor events intel: Update core event list for SkyLake Server
> perf vendor events intel: Update uncore event list for SkyLake Server
> perf vendor events: Update metrics for SkyLake Server
>
> .../arch/x86/cascadelakex/cache.json | 5468 ++++++++---------
> .../arch/x86/cascadelakex/clx-metrics.json | 253 +-
> .../arch/x86/cascadelakex/floating-point.json | 48 +-
> .../arch/x86/cascadelakex/frontend.json | 550 +-
> .../arch/x86/cascadelakex/memory.json | 5444 ++++++++--------
> .../arch/x86/cascadelakex/other.json | 4146 ++++++-------
> .../arch/x86/cascadelakex/pipeline.json | 1046 ++--
> .../arch/x86/cascadelakex/uncore-memory.json | 21 +-
> .../arch/x86/cascadelakex/uncore-other.json | 161 +-
> .../arch/x86/cascadelakex/virtual-memory.json | 256 +-
> .../pmu-events/arch/x86/skylakex/cache.json | 1724 +++---
> .../arch/x86/skylakex/floating-point.json | 56 +-
> .../arch/x86/skylakex/frontend.json | 580 +-
> .../pmu-events/arch/x86/skylakex/memory.json | 1300 ++--
> .../pmu-events/arch/x86/skylakex/other.json | 104 +-
> .../arch/x86/skylakex/pipeline.json | 1068 ++--
> .../arch/x86/skylakex/skx-metrics.json | 247 +-
> .../arch/x86/skylakex/uncore-memory.json | 9 -
> .../arch/x86/skylakex/uncore-other.json | 171 +-
> .../arch/x86/skylakex/virtual-memory.json | 288 +-
> 20 files changed, 11531 insertions(+), 11409 deletions(-)
>
> --
> 2.17.1
>
--
- Arnaldo
next prev parent reply other threads:[~2021-08-10 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 2:05 [PATCH 0/6] perf events update for CascadeLake server and SkyLake server Jin Yao
2021-08-10 2:05 ` [PATCH 1/6] perf vendor events intel: Update core event list for CascadeLake Server Jin Yao
2021-08-10 2:05 ` [PATCH 2/6] perf vendor events intel: Update uncore " Jin Yao
2021-08-10 2:05 ` [PATCH 3/6] perf vendor events: Update metrics " Jin Yao
2021-08-10 2:05 ` [PATCH 4/6] perf vendor events intel: Update core event list for SkyLake Server Jin Yao
2021-08-10 2:05 ` [PATCH 5/6] perf vendor events intel: Update uncore " Jin Yao
2021-08-10 2:05 ` [PATCH 6/6] perf vendor events: Update metrics " Jin Yao
2021-08-10 18:07 ` Arnaldo Carvalho de Melo [this message]
2021-08-10 18:21 ` [PATCH 0/6] perf events update for CascadeLake server and SkyLake server Arnaldo Carvalho de Melo
2021-08-11 0:28 ` Jin, Yao
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=YRLAWhHWX3oa0iyt@kernel.org \
--to=acme@kernel.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@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).