[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150126102711.GC15598@arm.com>
Date: Mon, 26 Jan 2015 10:27:11 +0000
From: Will Deacon <will.deacon@....com>
To: Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Felipe Balbi <balbi@...com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Tony Lindgren <tony@...mide.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Paul Mackerras <paulus@...ba.org>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: perf not capturing stack traces
On Sun, Jan 25, 2015 at 03:56:52PM +0000, Russell King - ARM Linux wrote:
> On Sat, Jan 24, 2015 at 04:23:42PM -0600, Felipe Balbi wrote:
> > yeah, I'll try a few older kernels, also see if I can reproduce on other
> > boards.
>
> Perf works for me with CONFIG_FRAME_POINTER=y, but that's only for kernel
> space, and for userspace where the programs have been built for ARM mode
> with frame pointers.
>
> The kernel may work without CONFIG_FRAME_POINTER set, but I've never
> tested that, and I'd suggest that (given my experience looking at oops
> dumps) it's not all that reliable.
>
> Lastly, userspace without frame pointers is pretty much hopeless.
FWIW, perf can now use libunwind for unwinding the userspace side of
things, so it's not quite as bad as it used to be. For the kernel side,
if the unwinder isn't working properly it would be nice to know *why*,
but I agree that it tends to be far flakier than the frame-pointer method.
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