From: adrian.hunter@intel.com (Adrian Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 2/2] perf tools: adding coresight etm PMU record capabilities
Date: Wed, 13 Jul 2016 14:40:59 +0300 [thread overview]
Message-ID: <578628CB.8020707@intel.com> (raw)
In-Reply-To: <1466182922-14426-3-git-send-email-mathieu.poirier@linaro.org>
On 17/06/16 20:02, Mathieu Poirier wrote:
> Coresight ETMs are IP blocks used to perform HW assisted tracing
> on a CPU core. This patch introduce the required auxiliary API
> functions allowing the perf core to interact with a tracer.
>
> Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> ---
> MAINTAINERS | 3 +
> tools/perf/arch/arm/util/Build | 2 +-
> tools/perf/arch/arm/util/auxtrace.c | 54 ++++
> tools/perf/arch/arm/util/cs-etm.c | 559 ++++++++++++++++++++++++++++++++++++
> tools/perf/arch/arm/util/cs-etm.h | 23 ++
> tools/perf/arch/arm64/util/Build | 4 +
> tools/perf/util/auxtrace.c | 1 +
> tools/perf/util/auxtrace.h | 1 +
> tools/perf/util/cs-etm.h | 74 +++++
> 9 files changed, 720 insertions(+), 1 deletion(-)
> create mode 100644 tools/perf/arch/arm/util/auxtrace.c
> create mode 100644 tools/perf/arch/arm/util/cs-etm.c
> create mode 100644 tools/perf/arch/arm/util/cs-etm.h
> create mode 100644 tools/perf/util/cs-etm.h
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d3451007718b..4fa03b03bfc5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1086,6 +1086,9 @@ F: Documentation/trace/coresight.txt
> F: Documentation/devicetree/bindings/arm/coresight.txt
> F: Documentation/ABI/testing/sysfs-bus-coresight-devices-*
> F: tools/perf/arch/arm/util/pmu.c
> +F: tools/perf/arch/arm/util/auxtrace.c
> +F: tools/perf/arch/arm/util/cs_etm.c
> +F: tools/perf/arch/arm/util/cs_etm.h
File names have changed from having '_' to '-'
Also FWIW there is now tools/perf/util/cs-etm.h
As last time, there is no decoder, which still begs the question: is there
anything you can actually do with the perf.data file?
Otherwise:
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
next prev parent reply other threads:[~2016-07-13 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 17:02 [PATCH RESEND 0/2] perf tools: coresight PMU recording capabilities Mathieu Poirier
2016-06-17 17:02 ` [PATCH RESEND 1/2] perf tools: making coresight PMU listable Mathieu Poirier
2016-07-13 11:40 ` Adrian Hunter
2016-06-17 17:02 ` [PATCH RESEND 2/2] perf tools: adding coresight etm PMU record capabilities Mathieu Poirier
2016-07-13 11:40 ` Adrian Hunter [this message]
2016-07-13 15:11 ` Mathieu Poirier
2016-07-13 15:15 ` Arnaldo Carvalho de Melo
2016-07-13 17:23 ` Mathieu Poirier
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=578628CB.8020707@intel.com \
--to=adrian.hunter@intel.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;
as well as URLs for NNTP newsgroup(s).