linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Sean V Kelley <seanvk.dev@oregontracks.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-perf-users@vger.kernel.org
Cc: skelley@amperecomputing.com,
	Peter Zijlstra <peterz@infradead.org>,
	Will Deacon <will.deacon@arm.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>,
	Namhyung Kim <namhyung@kernel.org>,
	William Cohen <wcohen@redhat.com>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH] perf vendor events arm64: Enable JSON events for eMAG
Date: Fri, 3 Aug 2018 15:41:06 +0100	[thread overview]
Message-ID: <d6d9db03-657e-005c-8aa2-d0b3b41acb47@huawei.com> (raw)
In-Reply-To: <20180803041811.17065-1-seanvk.dev@oregontracks.org>

On 03/08/2018 05:18, Sean V Kelley wrote:
> This patch adds the Ampere Computing eMAG file.  This platform
> follows the ARMv8 recommended IMPLEMENTATION DEFINED events, where
> applicable.
>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> Cc: Jiri Olsa <jolsa@redhat.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: John Garry <john.garry@huawei.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
> Cc: William Cohen <wcohen@redhat.com>
>
> Signed-off-by: Sean V Kelley <seanvk.dev@oregontracks.org>

Reviewed-by: John Garry <john.garry@huawei.com>

> ---
>  .../arch/arm64/ampere/emag/core-imp-def.json  | 32 +++++++++++++++++++
>  tools/perf/pmu-events/arch/arm64/mapfile.csv  |  1 +
>  2 files changed, 33 insertions(+)
>  create mode 100644 tools/perf/pmu-events/arch/arm64/ampere/emag/core-imp-def.json
>
> diff --git a/tools/perf/pmu-events/arch/arm64/ampere/emag/core-imp-def.json b/tools/perf/pmu-events/arch/arm64/ampere/emag/core-imp-def.json
> new file mode 100644
> index 000000000000..bc03c06c3918
> --- /dev/null
> +++ b/tools/perf/pmu-events/arch/arm64/ampere/emag/core-imp-def.json
> @@ -0,0 +1,32 @@
> +[
> +    {
> +        "ArchStdEvent": "L1D_CACHE_RD",
> +    },
> +    {
> +        "ArchStdEvent": "L1D_CACHE_WR",
> +    },
> +    {
> +        "ArchStdEvent": "L1D_CACHE_REFILL_RD",
> +    },
> +    {
> +        "ArchStdEvent": "L1D_CACHE_REFILL_WR",
> +    },
> +    {
> +        "ArchStdEvent": "L1D_TLB_REFILL_RD",
> +    },
> +    {
> +        "ArchStdEvent": "L1D_TLB_REFILL_WR",
> +    },
> +    {
> +        "ArchStdEvent": "L1D_TLB_RD",
> +    },
> +    {
> +        "ArchStdEvent": "L1D_TLB_WR",
> +    },
> +    {
> +        "ArchStdEvent": "BUS_ACCESS_RD",
> +   },
> +   {
> +        "ArchStdEvent": "BUS_ACCESS_WR",
> +   }
> +]
> diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv
> index f03e26ecb658..59cd8604b0bd 100644
> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv
> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv
> @@ -16,3 +16,4 @@
>  0x00000000420f5160,v1,cavium/thunderx2,core
>  0x00000000430f0af0,v1,cavium/thunderx2,core
>  0x00000000480fd010,v1,hisilicon/hip08,core
> +0x00000000500f0000,v1,ampere/emag,core

We could order by vendor/platform, but not so important as I see.

>

  reply	other threads:[~2018-08-03 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03  4:18 [PATCH] perf vendor events arm64: Enable JSON events for eMAG Sean V Kelley
2018-08-03 14:41 ` John Garry [this message]
2018-08-03 15:48   ` Arnaldo Carvalho de Melo

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=d6d9db03-657e-005c-8aa2-d0b3b41acb47@huawei.com \
    --to=john.garry@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ganapatrao.kulkarni@cavium.com \
    --cc=jolsa@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=seanvk.dev@oregontracks.org \
    --cc=skelley@amperecomputing.com \
    --cc=wcohen@redhat.com \
    --cc=will.deacon@arm.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).