linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jean.pihet@linaro.org (Jean Pihet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] perf: parse the dwarf backtrace info from .debug_frame section
Date: Wed,  4 Sep 2013 20:04:11 +0200	[thread overview]
Message-ID: <1378317854-25965-1-git-send-email-jean.pihet@linaro.org> (raw)

On ARM the debug info is not present in the .eh_frame sections but
in .debug_frame instead.

This patch uses libunwind to load and parse the dwarf debug info from
the .debug_frame section if no .eh_frame_hdr section is found; also it
sets the hooks in the perf_regs and libunwind code for ARM.

The generated perf has been tested on ARM/OMAP4 and x86_64, using the
following commands:
 perf record -g [dwarf] -- <binary>
 perf report --sort symbol --call-graph --stdio


Jean Pihet (1):
  perf: parse the .debug_frame section in case .eh_frame is not present

Will Deacon (2):
  ARM: perf: add support for perf regs API
  ARM: perf: wire up perf_regs and unwind support for ARM

 arch/arm/Kconfig                        |  2 +
 arch/arm/include/uapi/asm/Kbuild        |  1 +
 arch/arm/include/uapi/asm/perf_regs.h   | 23 +++++++++++
 arch/arm/kernel/Makefile                |  1 +
 arch/arm/kernel/perf_regs.c             | 30 ++++++++++++++
 tools/perf/arch/arm/Makefile            |  3 ++
 tools/perf/arch/arm/include/perf_regs.h | 54 +++++++++++++++++++++++++
 tools/perf/arch/arm/util/unwind.c       | 48 ++++++++++++++++++++++
 tools/perf/config/Makefile              |  7 +++-
 tools/perf/util/unwind.c                | 70 +++++++++++++++++++++++++--------
 10 files changed, 221 insertions(+), 18 deletions(-)
 create mode 100644 arch/arm/include/uapi/asm/perf_regs.h
 create mode 100644 arch/arm/kernel/perf_regs.c
 create mode 100644 tools/perf/arch/arm/include/perf_regs.h
 create mode 100644 tools/perf/arch/arm/util/unwind.c

-- 
1.7.11.7

             reply	other threads:[~2013-09-04 18:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 18:04 Jean Pihet [this message]
2013-09-04 18:04 ` [PATCH 1/3] ARM: perf: add support for perf regs API Jean Pihet
2013-09-05 13:21   ` Ard Biesheuvel
2013-09-04 18:04 ` [PATCH 2/3] ARM: perf: wire up perf_regs and unwind support for ARM Jean Pihet
2013-09-04 18:04 ` [PATCH 3/3] perf: parse the .debug_frame section in case .eh_frame is not present Jean Pihet
2013-09-05 12:45   ` Will Deacon
2013-09-05 13:05     ` Jean Pihet
2013-09-05 13:17       ` Ard Biesheuvel
2013-09-05 13:19         ` Will Deacon
2013-09-05 13:33           ` Jean Pihet
2013-09-05 15:29             ` Jean Pihet
2013-09-05 15:45               ` Ard Biesheuvel
2013-09-05 13:10     ` Ard Biesheuvel
2013-09-05 16:30   ` Jiri Olsa
2013-09-05 16:49     ` Jean Pihet
2013-09-06 10:17       ` Jiri Olsa
2013-09-06  9:31     ` Jean Pihet
2013-09-06 10:17       ` Jiri Olsa
2013-09-06 14:10         ` Jean Pihet
  -- strict thread matches above, loose matches on Subject: below --
2013-09-09 10:00 [PATCH 0/3] perf: parse the dwarf backtrace info from .debug_frame section Jean Pihet
2013-09-10  7:29 ` Jean Pihet
2013-09-12 12:07 ` Jean Pihet
2013-09-12 12:19   ` Peter Zijlstra
2013-09-12 12:28     ` Will Deacon

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=1378317854-25965-1-git-send-email-jean.pihet@linaro.org \
    --to=jean.pihet@linaro.org \
    --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).