From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Building perf from ptxdist
Date: Wed, 25 Oct 2017 11:28:54 +0200 [thread overview]
Message-ID: <1755919.HSWrFxr9eY@ada> (raw)
In-Reply-To: <94D4A88F8AC34646A5288D11318F5D5B24B79D73@GDUKADH841.uk1.r-org.net>
Hello Jon,
Am Mittwoch, 25. Oktober 2017, 09:16:29 CEST schrieb jon.bird@gd-ms.uk:
> Can anyone give me some guidelines as to how you could go about building
> perf (held with the kernel sources) under ptxdist. In particular, I need it
> to pick up libelf for enabling userspace tracing on target.
Go to menuconfig --> Core (libc, locales) --> kernel tools --> perf
It should just work activating and using it on target, if you set the right
kernel config options.
(It doesn't work on my target though, I asked about it on IRC lately, but got
no help. On a at91sam9g20 SoC with 32 MB of RAM leads to perf segfaulting on
start, and strace leads me to the assumption there's not enough memory. :-/ )
Greets
Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-10-25 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 9:16 jon.bird
2017-10-25 9:28 ` Alexander Dahl [this message]
2017-10-25 9:51 ` jon.bird
2017-10-25 11:06 ` Alexander Dahl
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=1755919.HSWrFxr9eY@ada \
--to=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
/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