From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ryan Johnson <ryan.johnson@cs.utoronto.ca>
Cc: Chulmin Kim <cmkim@core.kaist.ac.kr>, linux-perf-users@vger.kernel.org
Subject: Re: perf top -z not working?
Date: Mon, 22 Oct 2012 09:01:00 -0600 [thread overview]
Message-ID: <50855FAC.5020403@gmail.com> (raw)
In-Reply-To: <20121022144552.GB8775@ghostprotocols.net>
On 10/22/12 8:45 AM, Arnaldo Carvalho de Melo wrote:
To add to Arnaldo's instructions, here's how to get a copy of his tree:
mkdir perf.git
cd perf.git
git init
git add remote acme git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
git remote update
git checkout remotes/acme/perf/core
mkdir /tmp/pbuild
make -C tools/perf O=/tmp/pbuild
/tmp/pbuild/perf top -z
To try out a different version:
git checkout v3.0
make -C tools/perf
or v3.2, v3.4, etc.
Building perf is fairly quick and you do not have to install them --
just run the built binary.
>
> To build just the tools, on a /usr/src/linux or wherever you have the
> newer kernel sources:
>
> make -C tools/perf install
>
> Then make sure you use what is in your ~/bin/ before the standard path:
>
> export PATH=~/bin:$PATH
> hash -r
>
> Then try perf top -z again.
>
> - Arnaldo
>
next prev parent reply other threads:[~2012-10-22 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 12:26 perf top -z not working? Ryan Johnson
2012-10-17 13:49 ` Chulmin Kim
2012-10-22 1:46 ` Arnaldo Carvalho de Melo
2012-10-22 11:50 ` Ryan Johnson
2012-10-22 13:12 ` David Ahern
2012-10-22 14:10 ` Ryan Johnson
2012-10-22 14:13 ` Chulmin Kim
2012-10-22 14:15 ` Chulmin Kim
2012-10-22 14:45 ` Arnaldo Carvalho de Melo
2012-10-22 15:01 ` David Ahern [this message]
2012-10-22 16:04 ` Ryan Johnson
2012-10-23 6:04 ` Namhyung Kim
2012-10-23 16:10 ` David Ahern
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=50855FAC.5020403@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=cmkim@core.kaist.ac.kr \
--cc=linux-perf-users@vger.kernel.org \
--cc=ryan.johnson@cs.utoronto.ca \
/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.