linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: HUMMEL Michel <michel.hummel@thalesgroup.com>
Cc: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: Re: Perf 2.6.32-220.el6.x86_64 problem when recording 2 counters
Date: Thu, 24 May 2012 10:27:53 -0600	[thread overview]
Message-ID: <4FBE6189.4040400@gmail.com> (raw)
In-Reply-To: <15071_1337876344_4FBE5F78_15071_4976_1_932AC94CE5A51243A6F091BAFB3EE3E0028B23FD2E@THSONEA01CMS01P.one.grp>

On 5/24/12 10:19 AM, HUMMEL Michel wrote:
> Thanks for your help,
>
> I tried with a perf_3.2 binary but it gives me the same bad results.
> I Tried to read the old record, and also to generate a new one with the 3.2 binary.
>
> I am not sure to understand your suggestion with perf script and the -R option, can you give me more details please (sorry for my poor english).


RHEL6 and 2.6.32 is fairly old from perf's perspective. I have not 
looked at RHEL6 source to see how much of the upstream code was 
backported. However, the perf.data file *should* be compatible with 
upstream perf code.

So, in an attempt to better understand why you are not getting expected 
results:

1. Add -R to your record command:
perf record -R -e cycles,instructions \
    -o perf.data.cycles.instructions2 ./test_perfo2

2. Use the 3.2 version of the perf binary to analyze the file

perf_3.2 script -i perf.data.cycles.instructions2 > samples

Look at the samples file -- it will contain each sample and the event 
that triggered it (cycles or instructions). Does looking at each sample 
give some idea as to why the report does not make sense?

David

  reply	other threads:[~2012-05-24 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 16:06 Perf 2.6.32-220.el6.x86_64 problem when recording 2 counters HUMMEL Michel
2012-05-24  0:33 ` Michael Ellerman
2012-05-24  7:14   ` HUMMEL Michel
2012-05-24 14:57     ` David Ahern
2012-05-24 16:19       ` HUMMEL Michel
2012-05-24 16:27         ` David Ahern [this message]
2012-05-24  0:44 ` Namhyung Kim
2012-05-24  7:23   ` HUMMEL Michel

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=4FBE6189.4040400@gmail.com \
    --to=dsahern@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=michel.hummel@thalesgroup.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).