linux-kernel - Re: [PATCH 0/3] perf: parse the dwarf backtrace info from .debug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFrcx1mQ-P7byYfqP-0bYabUzTDeSWyHFx2FJQ6wQLYEcV_Pxw@mail.gmail.com>
Date:	Thu, 12 Sep 2013 14:07:23 +0200
From:	Jean Pihet <jean.pihet@...aro.org>
To:	Will Deacon <will.deacon@....com>, Jiri Olsa <jolsa@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	".Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: [PATCH 0/3] perf: parse the dwarf backtrace info from
 .debug_frame section

Hi,

-- Adding more maintainers in the To: list --

Ping about the patch set, is this one acceptable for mainline?

Jean

On 9 September 2013 12:00, Jean Pihet <jean.pihet@...aro.org> wrote:
> On ARM the debug info is not present in the .eh_frame sections but
> in .debug_frame instead, in dwarf format.
>
> This patch set 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 ARMv7.
>
> Dependencies:
>  . if present, libunwind >= 1.1 is needed to prevent a segfault when
>    parsing the dwarf info,
>  . libunwind needs to be configured with --enable-debug-frame
>    to prevent a linkage error. Note: --enable-debug-frame is automatically
>    selected on ARM).
>
> The generated perf has been tested on ARMv7/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 registers 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              |  9 +++--
>  tools/perf/util/unwind.c                | 71 +++++++++++++++++++++++++--------
>  10 files changed, 223 insertions(+), 19 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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/