From: jolsa@redhat.com (Jiri Olsa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/9] perf utils: add support for arch standard events
Date: Thu, 8 Feb 2018 14:55:49 +0100 [thread overview]
Message-ID: <20180208135549.GK10234@krava> (raw)
In-Reply-To: <1517939104-230881-6-git-send-email-john.garry@huawei.com>
On Wed, Feb 07, 2018 at 01:45:00AM +0800, John Garry wrote:
> For some architectures (like arm), there are architecture-
> defined events. Sometimes these events may be "recommended"
> according to the architecture standard, in that the
> implementer is free ignore the "recommendation" and create
> its custom event.
>
> This patch adds support for parsing standard events from
> arch-defined JSONs, and fixing up vendor events when they
> have implemented these events as standard.
>
> Support is also ensured that the vendor may implement their
> own custom events.
>
> A new step is added to the pmu events parsing to fix up the
> vendor events with the arch-standard events.
>
> The arch-defined JSONs must be placed in the arch root
> folder for preprocessing prior to tree JSON processing.
>
> In the vendor JSON, to specify that the arch event is
> supported, the keyword "ArchStdEvent" should be used,
> like this:
> [
> {
> "ArchStdEvent": "0x41",
> "BriefDescription": "L1D cache access, write"
> },
> ]
>
> No other JSON objects are strictly required. However,
> for other objects added, these take precedence over
> architecture defined standard events, thus supporting
> separate events which have the same event code.
>
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
> tools/perf/pmu-events/Build | 1 +
> tools/perf/pmu-events/README | 6 ++
> tools/perf/pmu-events/jevents.c | 185 +++++++++++++++++++++++++++++++++++++---
> 3 files changed, 182 insertions(+), 10 deletions(-)
>
> diff --git a/tools/perf/pmu-events/Build b/tools/perf/pmu-events/Build
> index 999a4e8..f9e8466 100644
> --- a/tools/perf/pmu-events/Build
> +++ b/tools/perf/pmu-events/Build
> @@ -1,5 +1,6 @@
> hostprogs := jevents
>
> +CHOSTFLAGS = -I$(srctree)/tools/include
Ithink this could be just CHOSTFLAGS_jevents.o = -I$(srctree)/tools/include
it's just for the list.h right?
jirka
next prev parent reply other threads:[~2018-02-08 13:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 17:44 [PATCH 0/9] perf events patches for improved ARM64 support John Garry
2018-02-06 17:44 ` [PATCH 1/9] perf vendor events: drop incomplete multiple mapfile support John Garry
2018-02-08 13:55 ` Jiri Olsa
2018-02-06 17:44 ` [PATCH 2/9] perf utils: add support for pmu events vendor sub-directory John Garry
2018-02-08 13:55 ` Jiri Olsa
2018-02-06 17:44 ` [PATCH 3/9] perf vendor events arm64: Relocate ThunderX2 JSON John Garry
2018-02-06 17:44 ` [PATCH 4/9] perf vendor events arm64: Relocate Cortex A53 JSONs John Garry
2018-02-06 17:45 ` [PATCH 5/9] perf utils: add support for arch standard events John Garry
2018-02-08 13:54 ` Jiri Olsa
2018-02-08 15:57 ` John Garry
2018-02-08 13:54 ` Jiri Olsa
2018-02-08 13:54 ` Jiri Olsa
2018-02-08 14:02 ` Alan Cox
2018-02-08 15:31 ` John Garry
2018-02-08 13:54 ` Jiri Olsa
2018-02-08 13:54 ` Jiri Olsa
2018-02-08 13:54 ` Jiri Olsa
2018-02-08 13:55 ` Jiri Olsa
2018-02-08 14:45 ` John Garry
2018-02-08 14:54 ` Jiri Olsa
2018-02-08 13:55 ` Jiri Olsa
2018-02-08 13:55 ` Jiri Olsa
2018-02-08 15:25 ` John Garry
2018-02-09 8:53 ` Jiri Olsa
2018-02-08 13:55 ` Jiri Olsa [this message]
2018-02-08 14:59 ` John Garry
2018-02-06 17:45 ` [PATCH 6/9] perf utils: add armv8-recommended.json John Garry
2018-02-06 17:45 ` [PATCH 7/9] perf utils: fixup Cavium ThunderX2 JSON to use ARMv8 recommended events John Garry
2018-02-06 17:45 ` [PATCH 8/9] perf utils: fixup ARM Cortex A53 JSONs " John Garry
2018-02-06 17:45 ` [PATCH 9/9] perf utils: add HiSilicon hip08 JSON file John Garry
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=20180208135549.GK10234@krava \
--to=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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