[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140709140427.GP9485@arm.com>
Date: Wed, 9 Jul 2014 15:04:28 +0100
From: Will Deacon <will.deacon@....com>
To: Jean Pihet <jean.pihet@...aro.org>
Cc: "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>,
Jiri Olsa <jolsa@...hat.com>, Ingo Molnar <mingo@...nel.org>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
"steve.capper@...aro.org" <steve.capper@...aro.org>
Subject: Re: [PATCH 0/3] ARM: perf: allow tracing with kernel tracepoints
events
Hi Jean,
On Mon, Jul 07, 2014 at 02:45:07PM +0100, Jean Pihet wrote:
> - Robustify the user backtrace code, as done on other architectures.
> - Provide the symbols resolution when triggering from tracepoints.
>
> Big thanks to Steve Capper for the help in debugging and rephrasing the
> commits descriptions.
>
> Stress tested with perf record and tracepoints triggering (-e <tracepoint>),
> with unwinding using fp (--call-graph fp) and dwarf info (--call-graph dwarf).
I've taken the first two in this series, but patch 3 still doesn't address
my concerns about saving the required register state for unwinding.
Thanks!
Will
--
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/
Powered by blists - more mailing lists