linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Maynard Johnson <maynardj@us.ibm.com>
Cc: linux-perf-users@vger.kernel.org, suka@us.ibm.com
Subject: Re: --mmap-pages option seemingly has no effect to help with LOST samples
Date: Fri, 22 Jun 2012 13:44:33 -0600	[thread overview]
Message-ID: <4FE4CB21.90005@gmail.com> (raw)
In-Reply-To: <4FE4C589.5080802@us.ibm.com>

On 6/22/12 1:20 PM, Maynard Johnson wrote:
> I was seeing this on both my Intel Core 2 Duo and an IBM POWER7 server, both running RHEL 6.2.  Also tried on another POWER7 running RHEL 6.3 beta, and got the same results.  I found another POWER server that had RHEL 6.2 but was temporarily booted on a 3.5 kernel and ran the test there -- the counts were good there. :-)  Just to be sure, I rebooted that system to the stock RHEL 6.2 kernel and reproduced the problem.  So it seems there's an upstream fix for this.  Can someone help me find the commit?

emails crossing in the ether.

2.6.32 is real early in the perf history. I flipped a system to the 
Fedora 14 2.6.35.14 kernel -- and it does not handle multiple events 
either. With Arnaldo's last updates I did notice something curious about 
the events:

Aggregated stats:
            TOTAL events:      13165
             MMAP events:         63
             COMM events:          2
           SAMPLE events:      13100
cycles:HG stats:
            TOTAL events:       5769
             MMAP events:         63
             COMM events:          2
           SAMPLE events:       5704
instructions:HG stats:
            TOTAL events:       7396
           SAMPLE events:       7396

The HG is wrong -- I did not put attributes on the event. So, re-running 
with uk:

$ perf record -fo /tmp/perf.data -e cycles:uk -e instructions:uk -c 
100000 /tmp/loop_1b_instructions

And life turned out right:
Aggregated stats:
            TOTAL events:      17967
             MMAP events:         63
             COMM events:          2
             EXIT events:          1
           SAMPLE events:      17901
cycles:ku stats:
            TOTAL events:       7862
             MMAP events:         63
             COMM events:          2
             EXIT events:          1
           SAMPLE events:       7796
instructions:ku stats:
            TOTAL events:      10105
           SAMPLE events:      10105

So, try adding :uk to your events.

David

  reply	other threads:[~2012-06-22 19:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 20:55 --mmap-pages option seemingly has no effect to help with LOST samples Maynard Johnson
2012-06-12 21:05 ` David Ahern
2012-06-13 15:35   ` Maynard Johnson
2012-06-13 15:48     ` David Ahern
2012-06-22 15:59       ` Maynard Johnson
2012-06-22 16:16         ` David Ahern
2012-06-22 19:20           ` Maynard Johnson
2012-06-22 19:44             ` David Ahern [this message]
2012-06-22 20:23               ` Maynard Johnson
2012-06-22 20:38                 ` David Ahern
2012-06-25 14:10                   ` Maynard Johnson
2012-06-26 20:16                     ` David Ahern
2012-06-26 20:32                       ` Maynard Johnson
2012-06-22 19:23         ` 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=4FE4CB21.90005@gmail.com \
    --to=dsahern@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=maynardj@us.ibm.com \
    --cc=suka@us.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).