mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Shunsuke Nakamura <nakamura.shun@jp.fujitsu.com>,
	<will@kernel.org>, <mathieu.poirier@linaro.org>,
	<leo.yan@linaro.org>, <peterz@infradead.org>, <mingo@redhat.com>,
	<acme@kernel.org>, <mark.rutland@arm.com>,
	<alexander.shishkin@linux.intel.com>, <jolsa@redhat.com>,
	<namhyung@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Shunsuke Nakamura <nakamura.shun@fujitsu.com>
Subject: Re: [PATCH v5 0/4] perf vendor events: Support PMU events for A64FX
Date: Tue, 2 Feb 2021 16:43:06 +0000	[thread overview]
Message-ID: <57c6b89d-e0b2-3df4-8dcf-2cc71f772cb4@huawei.com> (raw)
In-Reply-To: <20210202125140.1785583-1-nakamura.shun@jp.fujitsu.com>

On 02/02/2021 12:51, Shunsuke Nakamura wrote:
> From: Shunsuke Nakamura <nakamura.shun@fujitsu.com>
> 
> This patch series supports A64FX PMU event v1.2.
> 
> The first patch adds a common and microarchitecture event, which can be
> referenced from CPU JSONs.
> This patch uses part of John's patch.[1]
> 
> The second patch add more common and microarchitecture events.
> 
> The third patch fixes the lexical definition of event name so that
> perf can recognize event name that start with a number.
> 
> The fourth patch adds PMU events for A64FX.

Just some things to note:
- please pick up and apply reviewed-by tags granted from previous 
reviews if explicitly granted, subject to making any trivial changes 
requested
If any significant changes are made, then don't pick up theses tags or 
drop them (if they were picked up earlier)
- I'd say that it's best not to send my patch in 1/4, but better to 
mention the series which this is based on in your cover letter
Sending my patch is only going to make the maintainers (Arnaldo) life 
more difficult to track these things.

Apart from that, I think that we're a bit uncertain about patch 3/4

Thanks,
john


> 
> 
> Changes in v4:
>   - Add arm64 to the subjects of the second and fourth patches.
>   - Add reference URLs to the body of the second patch.
> 
> Changes in v3:
>   - Add linux-arm-kernel mailing list to cc.
> 
> Changes in v2:
>   - Added armv8-common-and-microarch based on John's patch.[1]
>   - Fixed A64FX Json to refer to standard events in armv8-common-and-microarch.
> 
> 
> [1] https://lore.kernel.org/lkml/1611835236-34696-3-git-send-email-john.garry@huawei.com/
> 
> 
> John Garry (1):
>    perf vendor events arm64: Add common and uarch event JSON
> 
> Shunsuke Nakamura (3):
>    perf vendor events arm64: Add common and uarch event JSON
>    perf vendor events arm64: Add more common and uarch events
>    perf tools: Fix lexical definition of event name
>    perf vendor events arm64: Add Fujitsu A64FX pmu event
> 
>   .../arch/arm64/armv8-common-and-microarch.json     | 476 +++++++++++++++++++++
>   .../arch/arm64/fujitsu/a64fx/branch.json           |   8 +
>   .../pmu-events/arch/arm64/fujitsu/a64fx/bus.json   |  62 +++
>   .../pmu-events/arch/arm64/fujitsu/a64fx/cache.json | 128 ++++++
>   .../pmu-events/arch/arm64/fujitsu/a64fx/cycle.json |   5 +
>   .../arch/arm64/fujitsu/a64fx/exception.json        |  29 ++
>   .../arch/arm64/fujitsu/a64fx/instruction.json      | 131 ++++++
>   .../arch/arm64/fujitsu/a64fx/memory.json           |   8 +
>   .../pmu-events/arch/arm64/fujitsu/a64fx/other.json | 188 ++++++++
>   .../arch/arm64/fujitsu/a64fx/pipeline.json         | 194 +++++++++
>   .../pmu-events/arch/arm64/fujitsu/a64fx/sve.json   | 110 +++++
>   tools/perf/pmu-events/arch/arm64/mapfile.csv       |   1 +
>   tools/perf/util/parse-events.l                     |   2 +-
>   13 files changed, 1341 insertions(+), 1 deletion(-)
>   create mode 100644 tools/perf/pmu-events/arch/arm64/armv8-common-and-microarch.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/branch.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/bus.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/cache.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/cycle.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/exception.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/instruction.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/memory.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/other.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/pipeline.json
>   create mode 100644 tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/sve.json
> 


  parent reply	other threads:[~2021-02-02 16:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 12:51 Shunsuke Nakamura
2021-02-02 12:51 ` [PATCH v5 1/4] perf vendor events arm64: Add common and uarch event JSON Shunsuke Nakamura
2021-02-02 12:51 ` [PATCH v5 2/4] perf vendor events arm64: Add more common and uarch events Shunsuke Nakamura
2021-02-02 12:51 ` [PATCH v5 3/4] perf tools: Fix lexical definition of event name Shunsuke Nakamura
2021-02-02 12:51 ` [PATCH v5 4/4] perf vendor events arm64: Add Fujitsu A64FX pmu event Shunsuke Nakamura
2021-02-02 16:43 ` John Garry [this message]
2021-02-03  7:02   ` [PATCH v5 0/4] perf vendor events: Support PMU events for A64FX nakamura.shun
2021-02-05 12:09     ` nakamura.shun
2021-02-08  1:53       ` nakamura.shun
2021-02-08  8:57         ` John Garry
     [not found]           ` <OSBPR01MB46003F3F8106E1AA231084D9F78D9@OSBPR01MB4600.jpnprd01.prod.outlook.com>
2021-02-10 15:48             ` John Garry
2021-02-10 16:36               ` nakamura.shun

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=57c6b89d-e0b2-3df4-8dcf-2cc71f772cb4@huawei.com \
    --to=john.garry@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=nakamura.shun@fujitsu.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

Powered by JetHome