From: Andrew Parlane <andrewp@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Perf questions on a 3.10.17 kernel on IMX6
Date: Thu, 27 Nov 2014 12:05:18 +0000 [thread overview]
Message-ID: <5477137E.4090303@carallon.com> (raw)
Hi,
I'm attempting to do some profiling of a QT5 application on an IMX6
running a 3.10.17 kernel, based of a boundary devices BSP. All built
through buildroot 2014.08
Firstly to get perf to build I needed to apply a patch to
linux/tools/lib/lk/Makefile to get it to honour cross compiling. I found
the commit in the 3.12.33 branch of the kernel.org GIT.
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/tools/lib/lk/Makefile?id=3c4797d46c14fa0c7cf733a77bd4b28875078b53
Running "perf test -v" it doesn't look so happy. Output log here:
http://slexy.org/view/s21a2Nugr8
I'm having problems getting debug symbols in the output. I've spent a
couple of days reading up on perf and trying various options. I can get
some kernel debug symbols, but nothing from userspace. I'm pretty sure
I've built my app with -Og -ggdb -fno-omit-frame-pointer -Wl,--build-id.
If anyone has any suggestions, that would be useful.
My other question is has anyone had any success recording on a target
environment and then analysing on the build machine? Allowing debug
symbols to be supplied only on the build machine? I got perf built for
the host using buildroot, it runs but I still don't see debug symbols,
and I can't see how to pass in a binary with debug symbols for it to use
(like you would using gdbserver on the target and gdb on the host).
If anyone has any advice on using perf like this, it would be much
appreciated.
Thanks,
Andrew Parlane
Carallon LTD.
reply other threads:[~2014-11-27 12:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5477137E.4090303@carallon.com \
--to=andrewp@carallon.com \
--cc=buildroot@busybox.net \
/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