All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Davidoff <davidoff@qedmf.net>
To: David Ahern <dsahern@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Getting started with perf; a couple of questions
Date: Fri, 31 May 2013 01:09:18 -0600	[thread overview]
Message-ID: <CAJLXCZTzRdLYmcRVTO_AeRawmZ55AtdABcKpu5T5A-Z89iHnbA@mail.gmail.com> (raw)
In-Reply-To: <51A83824.1090907@gmail.com>

Hi,

Thanks for the quick response.

> add a -v and see if more info comes out.
>
> perf script can be used to dump events.

I tried again with -v on record, but I am still not getting any event
samples in perf.data. Looking at an ASCII dump with report -D, I see
43 PERF_RECORD_MMAP entries, each of which appears to be related to a
kernel module, but nothing for any of the events I have selected to
sample (each is simply listed like "page-faults stats:").

The run ends like this every time:

[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.004 MB perf.data (~194 samples) ]

"Woken up 1 times" seemed suspicious, if record should be sampling at
1000Hz. I tried using -F 1000 and adding cycles to my events list both
in an effort to get 1000Hz samples, but as far as I could tell, there
was no change in the recorded data.

Also note that when using -v with record, I get the message "failed to
write feature 2" at the very end of the run output. I do not get that
message without -v. I don't know what it's trying to tell me and
haven't looked at the source code yet.

The command I am running is a threaded python script (spawns workers).
As I understand the documentation, I shouldn't need any additional
flags for perf to collect data on all the threads, since it reads like
counter inheritance is on by default. In other words, I believe perf
record should be working in what is documented as "per-process" mode
by default. I tried using -i with record in case I wasn't
understanding correctly, but that didn't change anything.

I will play with this more tomorrow but any further advice is
appreciated. I feel like I'm probably just missing a switch or
something that's not entirely obvious from the scant documentation I
have found.

Thanks again.
Andy

  reply	other threads:[~2013-05-31  7:09 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
2013-05-31  7:09   ` Andrew Davidoff [this message]
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=CAJLXCZTzRdLYmcRVTO_AeRawmZ55AtdABcKpu5T5A-Z89iHnbA@mail.gmail.com \
    --to=davidoff@qedmf.net \
    --cc=dsahern@gmail.com \
    --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.