mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: <jon.bird@gd-ms.uk>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Building perf from ptxdist
Date: Wed, 25 Oct 2017 09:51:05 +0000	[thread overview]
Message-ID: <94D4A88F8AC34646A5288D11318F5D5B24B79DF4@GDUKADH841.uk1.r-org.net> (raw)
In-Reply-To: <1755919.HSWrFxr9eY@ada>

Hi Alexander,

On 2017-10-25, Alexander Dahl wrote:

> 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.
> 
I don't have that option in the version of ptxdist I'm using (2016-04) so I'm guessing this is a fairly new option then? Either way, that's helpful because I can probably just lift the necessary scripts etc. into my existing version or do an upgrade.

> (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.
> :-/ )
> 
I have a little more RAM on my target board than that so hopefully I won't run into that problem.

Thanks,

Jon.

--
Jon Bird, CEng MBCS
Software Engineer
Electronic Systems
General Dynamics United Kingdom Ltd.
Castleham Road, St Leonards on Sea, East Sussex, TN38 9NJ

Telephone: +441424798278
Email: jon.bird@gd-ms.uk
Website: www.generaldynamics.uk.com      


------------------------------------------------------------------------------

This email and any files attached are intended for the addressee and may contain information of a confidential nature. If you are not the intended recipient, be aware that this email was sent to you in error and you should not disclose, distribute, print, copy or make other use of this email or its attachments. Such actions, in fact, may be unlawful. In compliance with the various Regulations and Acts, General Dynamics United Kingdom Limited reserves the right to monitor (and examine for viruses) all emails and email attachments, both inbound and outbound. Email communications and their attachments may not be secure or error- or virus-free and the company does not accept liability or responsibility for such matters or the consequences thereof. General Dynamics United Kingdom Limited, Registered Office: 21 Holborn Viaduct, London EC1A 2DY. Registered in England and Wales No: 1911653.
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-10-25  9:51 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
2017-10-25  9:51   ` jon.bird [this message]
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=94D4A88F8AC34646A5288D11318F5D5B24B79DF4@GDUKADH841.uk1.r-org.net \
    --to=jon.bird@gd-ms.uk \
    --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