linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
	<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
	<jolsa@redhat.com>, <namhyung@kernel.org>, <irogers@google.com>,
	<kjain@linux.ibm.com>
Cc: <linux-kernel@vger.kernel.org>, <linuxarm@openeuler.org>,
	<james.clark@arm.com>, <nakamura.shun@jp.fujitsu.com>,
	Will Deacon <will@kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Leo Yan <leo.yan@linaro.org>,
	"Mathieu Poirier" <mathieu.poirier@linaro.org>
Subject: Re: [PATCH 0/4] perf vendor events arm64: Some tidy-up/refactoring
Date: Mon, 25 Jan 2021 12:49:04 +0000	[thread overview]
Message-ID: <a8533b41-ef64-4584-4a65-ca605d6e4acb@huawei.com> (raw)
In-Reply-To: <1611575600-2440-1-git-send-email-john.garry@huawei.com>

On 25/01/2021 11:53, John Garry wrote:

+ Missed reviewers for 
https://lore.kernel.org/lkml/1611575600-2440-1-git-send-email-john.garry@huawei.com/T/#u

> There is much event duplication in the common and uarch events for A76
> and Ampere eMag support, so factor out into a common JSON.
> 
> Since the wording for events may differ between CPU datasheet and
> the architecture reference manual, the current wording is kept. This
> is unless there are minor differences. In addition, event names are
> renamed to be same as architecture reference manual, to keep commonality.
> 
> Also a minor fix is included for the Ampere eMag JSON.
> 
> John Garry (4):
>    perf vendor events arm64: Fix Ampere eMag event typo
>    perf vendor events arm64: Add common and uarch event JSON
>    perf vendor events arm64: Reference common and uarch events for Ampere
>      eMag
>    perf vendor events arm64: Reference common and uarch events for A76
> 
>   .../arch/arm64/ampere/emag/branch.json        |   8 +-
>   .../arch/arm64/ampere/emag/bus.json           |   5 +-
>   .../arch/arm64/ampere/emag/cache.json         |  58 +---
>   .../arch/arm64/ampere/emag/clock.json         |   4 +-
>   .../arch/arm64/ampere/emag/exception.json     |  10 +-
>   .../arch/arm64/ampere/emag/instruction.json   |  34 +--
>   .../arch/arm64/ampere/emag/memory.json        |  11 +-
>   .../arch/arm64/arm/cortex-a76-n1/branch.json  |  12 +-
>   .../arch/arm64/arm/cortex-a76-n1/bus.json     |  19 +-
>   .../arch/arm64/arm/cortex-a76-n1/cache.json   | 118 +++------
>   .../arm64/arm/cortex-a76-n1/exception.json    |  10 +-
>   .../arm64/arm/cortex-a76-n1/instruction.json  |  45 +---
>   .../arch/arm64/arm/cortex-a76-n1/memory.json  |   6 +-
>   .../arch/arm64/arm/cortex-a76-n1/other.json   |   4 +-
>   .../arm64/arm/cortex-a76-n1/pipeline.json     |  12 +-
>   .../arm64/armv8-common-and-microarch.json     | 248 ++++++++++++++++++
>   16 files changed, 356 insertions(+), 248 deletions(-)
>   create mode 100644 tools/perf/pmu-events/arch/arm64/armv8-common-and-microarch.json
> 


      parent reply	other threads:[~2021-01-26  6:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 11:53 [PATCH 0/4] perf vendor events arm64: Some tidy-up/refactoring John Garry
2021-01-25 11:53 ` [PATCH 1/4] perf vendor events arm64: Fix Ampere eMag event typo John Garry
2021-01-25 11:53 ` [PATCH 2/4] perf vendor events arm64: Add common and uarch event JSON John Garry
2021-01-28  5:30   ` nakamura.shun
2021-01-28  8:41     ` John Garry
2021-01-25 11:53 ` [PATCH 3/4] perf vendor events arm64: Reference common and uarch events for Ampere eMag John Garry
2021-01-25 11:53 ` [PATCH 4/4] perf vendor events arm64: Reference common and uarch events for A76 John Garry
2021-01-25 12:49 ` John Garry [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=a8533b41-ef64-4584-4a65-ca605d6e4acb@huawei.com \
    --to=john.garry@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@arm.com \
    --cc=jolsa@redhat.com \
    --cc=kjain@linux.ibm.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=nakamura.shun@jp.fujitsu.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).