From: balbi@ti•com (Felipe Balbi)
To: linux-arm-kernel@lists•infradead.org
Subject: perf not capturing stack traces
Date: Sat, 24 Jan 2015 16:23:42 -0600 [thread overview]
Message-ID: <20150124222342.GA26941@saruman.tx.rr.com> (raw)
In-Reply-To: <20150124151204.GF3073@kernel.org>
Hi,
On Sat, Jan 24, 2015 at 12:12:04PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jan 23, 2015 at 04:37:45PM -0600, Felipe Balbi escreveu:
> > On Fri, Jan 23, 2015 at 05:59:59PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Fri, Jan 23, 2015 at 01:51:28PM -0600, Felipe Balbi escreveu:
> > > > I'm using v3.19-rc5 on an ARM Cortex A9 board. Unfortunately, perf is
> > > > not able to capture any stack traces even though I CONFIG_STACKTRACE,
> > > > CONFIG_FRAME_POINTER and CONFIG_ARM_UNWIND all enabled.
> > > >
> > > > I wonder if anybody else is facing similar issues.
> > >
> > > Did it work with a previous kernel?
> >
> > haven't checked with this board. First time I tried to use perf for
> > anything.
>
> And it is the first time I've heard about such a problem, not dealing
> with ARM myself, so I guess this is a case for looking if there was some
> previous kernel where this worked, then trying to bisect where the
> problem was introduced :-\
yeah, I'll try a few older kernels, also see if I can reproduce on other
boards.
cheers
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150124/4836ee3f/attachment.sig>
next prev parent reply other threads:[~2015-01-24 22:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 19:51 perf not capturing stack traces Felipe Balbi
2015-01-23 19:53 ` Felipe Balbi
2015-01-23 20:59 ` Arnaldo Carvalho de Melo
2015-01-23 22:37 ` Felipe Balbi
2015-01-24 15:12 ` Arnaldo Carvalho de Melo
2015-01-24 22:23 ` Felipe Balbi [this message]
2015-01-25 15:56 ` Russell King - ARM Linux
2015-01-26 10:27 ` Will Deacon
2015-01-26 12:12 ` Arnaldo Carvalho de Melo
2015-01-26 12:16 ` Will Deacon
2015-01-26 12:29 ` Arnaldo Carvalho de Melo
2015-01-26 13:54 ` Russell King - ARM Linux
2015-01-26 14:33 ` Arnaldo Carvalho de Melo
2015-01-26 13:51 ` Russell King - ARM Linux
2015-01-26 14:37 ` Arnaldo Carvalho de Melo
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=20150124222342.GA26941@saruman.tx.rr.com \
--to=balbi@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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