From: Chris Ryder <chris.ryder@arm.com>
To: linux-kernel@vger.kernel.org
Cc: Chris Ryder <chris.ryder@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-perf-users@vger.kernel.org,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: [PATCH 0/7] perf annotate: Support for AArch64
Date: Thu, 19 May 2016 17:59:44 +0100 [thread overview]
Message-ID: <cover.1463676839.git.chris.ryder@arm.com> (raw)
Hi,
The linux perf tool has some basic support for annotating
AArch32 branch instructions when displaying assembly. This
patchset refactors the annotation support to have a cleaner
separation between architectures, and then adds support for
annotating AArch64 instructions.
Comments very welcome, thanks.
Chris.
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: linux-perf-users@vger.kernel.org
Cc: Will Deacon <will.deacon@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Chris Ryder (7):
perf annotate: Fix identification of ARM blt and bls instructions
perf annotate: Sort list of recognised instructions
pref annotate: Separate architecture specific annotation support
perf annotate: Separate out architecture specific parsing
perf annotate: Architecture neutral handling of return instruction
perf annotate: Make action message be architecture specific
perf annotate: AArch64 support
tools/perf/arch/arm/include/annotate_ins.h | 27 +++++
tools/perf/arch/arm/util/Build | 2 +
tools/perf/arch/arm/util/annotate_ins.c | 22 ++++
tools/perf/arch/arm64/include/annotate_ins.h | 40 +++++++
tools/perf/arch/arm64/util/Build | 2 +
tools/perf/arch/arm64/util/annotate_ins.c | 21 ++++
tools/perf/arch/x86/include/annotate_ins.h | 84 +++++++++++++++
tools/perf/arch/x86/util/Build | 1 +
tools/perf/arch/x86/util/annotate_ins.c | 17 +++
tools/perf/config/Makefile | 12 +++
tools/perf/ui/browsers/annotate.c | 15 +--
tools/perf/util/Build | 1 +
tools/perf/util/annotate.c | 150 +++++++--------------------
tools/perf/util/annotate_ins.c | 21 ++++
tools/perf/util/annotate_ins.h | 17 +++
15 files changed, 313 insertions(+), 119 deletions(-)
create mode 100644 tools/perf/arch/arm/include/annotate_ins.h
create mode 100644 tools/perf/arch/arm/util/annotate_ins.c
create mode 100644 tools/perf/arch/arm64/include/annotate_ins.h
create mode 100644 tools/perf/arch/arm64/util/annotate_ins.c
create mode 100644 tools/perf/arch/x86/include/annotate_ins.h
create mode 100644 tools/perf/arch/x86/util/annotate_ins.c
create mode 100644 tools/perf/util/annotate_ins.c
create mode 100644 tools/perf/util/annotate_ins.h
--
2.1.4
next reply other threads:[~2016-05-19 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 16:59 Chris Ryder [this message]
2016-05-19 16:59 ` [PATCH 1/7] perf annotate: Fix identification of ARM blt and bls instructions Chris Ryder
2016-05-19 16:59 ` [PATCH 2/7] perf annotate: Sort list of recognised instructions Chris Ryder
2016-05-19 16:59 ` [PATCH 3/7] pref annotate: Separate architecture specific annotation support Chris Ryder
2016-05-19 19:45 ` Arnaldo Carvalho de Melo
2016-05-20 9:44 ` Chris Ryder
2016-05-19 16:59 ` [PATCH 4/7] perf annotate: Separate out architecture specific parsing Chris Ryder
2016-05-19 16:59 ` [PATCH 5/7] perf annotate: Architecture neutral handling of return instruction Chris Ryder
2016-05-19 16:59 ` [PATCH 6/7] perf annotate: Make action message be architecture specific Chris Ryder
2016-05-19 16:59 ` [PATCH 7/7] perf annotate: AArch64 support Chris Ryder
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=cover.1463676839.git.chris.ryder@arm.com \
--to=chris.ryder@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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).