From: David Ahern <dsahern@gmail.com>
To: Andrew Davidoff <davidoff@qedmf.net>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Getting started with perf; a couple of questions
Date: Thu, 30 May 2013 23:41:56 -0600 [thread overview]
Message-ID: <51A83824.1090907@gmail.com> (raw)
In-Reply-To: <CAJLXCZTs4i0P3wA78u25aCt-rfcsBNQ8t0QSsbWazQyoV-XdLA@mail.gmail.com>
On 5/30/13 11:26 PM, Andrew Davidoff wrote:
> Hi,
>
> I am getting started with perf and have a couple of questions.
>
> * Does the version of perf being used need to be built from the source
> for the running kernel, or is it supported to use a build from a newer
> kernel source? I am currently running perf built from 3.9.4 kernel
> sources on a machine running kernel 2.6.32.
In general, perf userspace from upstream can work with any kernel
version. The only problem I can recall is 2.6.31 -- ie., upstream does
not work with 2.6.31 and prior.
>
> * I am getting event output with a specific `perf stat` invocation,
> but when I run the same invocation under `perf record`, `perf report`
> complains "The perf.data file has no samples". Why would that be? The
> invocation looks like this:
>
> perf record -e cache-misses,page-faults,minor-faults,major-faults,cpu-migrations,L1-dcache-load-misses,L1-dcache-store-misses,L1-icache-load-misses,LLC-load-misses,LLC-store-misses,dTLB-load-misses,dTLB-store-misses,iTLB-load-misses
> -- {program} {arg} {arg} ... {arg}
add a -v and see if more info comes out.
perf script can be used to dump events.
David
next prev parent reply other threads:[~2013-05-31 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 5:26 Getting started with perf; a couple of questions Andrew Davidoff
2013-05-31 5:41 ` David Ahern [this message]
2013-05-31 7:09 ` Andrew Davidoff
2013-05-31 20:35 ` Andrew Davidoff
2013-06-06 14:01 ` David Ahern
2013-06-06 18:26 ` Andrew Davidoff
2013-06-07 15:05 ` David Ahern
2013-06-07 23:49 ` Andrew Davidoff
2013-06-08 0:08 ` 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=51A83824.1090907@gmail.com \
--to=dsahern@gmail.com \
--cc=davidoff@qedmf.net \
--cc=linux-perf-users@vger.kernel.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.