All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Amit Tomer <amittomer25@gmail.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: How to Set up Perf tool
Date: Fri, 1 Nov 2013 14:52:33 -0400	[thread overview]
Message-ID: <5273F871.9090206@windriver.com> (raw)
In-Reply-To: <CABHD4K9q7=RK_3B2HUPR9J0RoLZPBQ5-qwY3qjYeRLajs-gnhQ@mail.gmail.com>

On 13-11-01 12:40 PM, Amit Tomer wrote:
> We have a requirement here to set up the perf tool through our Yocto
> frame work.
>
> As Perf source comes with linux kernel under tools/perf ,so it should be
> compiled with kernel recipe itself.
>
> But after bitbake of our kernel recipe,we couldn't find any binary
> related to perf.
> we made sure that below variable should be set in kernel config file
>
> CONFIG_HAVE_PERF_EVENTS=y
> CONFIG_PERF_EVENTS=y
>
> Do we need to make any change to our kernel recipe file as well??
>
> Can anyone let us know how we should set Perf tool.

It depends on the version of the the project and the kernel you are
using, but there's a separate perf recipe, and has been for quite a
while.

That perf builds out of the staged kernel source, which is put
in place as part of the kernel build.

Try an old fashioned: bitbake perf

And see what you get. If you want it to be built and installed into
your rootfs, you'll need to arrange to get it into your image's
installed package list.

Bruce


>
> Thanks
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



  reply	other threads:[~2013-11-01 18:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 16:40 How to Set up Perf tool Amit Tomer
2013-11-01 18:52 ` Bruce Ashfield [this message]
2013-11-01 20:19   ` Amit Tomer

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=5273F871.9090206@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=amittomer25@gmail.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.