linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 07 Jun 2013 18:08:53 -0600	[thread overview]
Message-ID: <51B27615.3090504@gmail.com> (raw)
In-Reply-To: <CAJLXCZTayKKetZPx5mgsFm4wbnHnT__Hosqj-mBGnTXoTaiVjw@mail.gmail.com>

On 6/7/13 5:49 PM, Andrew Davidoff wrote:

> You are correct that the Ubuntu 10.04 host that doesn't seem to be
> recording properly is running a 2.6.32 kernel (2.6.32-47-server from
> Ubuntu). The invocation of perf record is the same as described for
> the CentOS VM (i.e. I am not using -p, and would like to not use -a,
> though -a is the only way I'm getting samples recorded for
> <command-to-trace>).

CentOS 6 has newer perf code than its kernel version suggests -- 
compliments of the RHEL backporting Jiri does.

>
> I had moved to building a newer version of perf than the one that came
> from the Ubuntu 10.04 repo (linux-tools-common) because that one
> appeared ancient based on the output it was generating, and reports
> version as 0.0.2.PERF (though the binary is installed as
> /usr/bin/perf_2.6.32-47). perf record does record data with that
> version, but it looks like (via perf report) that it's data only for
> one event even when multiple are passed, and that event isn't labeled
> in the report, so at a glance I am not sure which it is.

If the original perf command works but newer versions do not then the 
compatibility wheels have fallen off somewhere along the line.

Most likely CentOS 6 works b/c of the backports.

David

>
> Anyway, for now I'm not worrying about getting this working on this
> particular version of Ubuntu, but I appreciate all your help. If I
> decide to dig further I'll start iterating through the versions you
> suggested and see where things get extra broken.
>
> Andy
>

      reply	other threads:[~2013-06-08  0:08 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
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 [this message]

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=51B27615.3090504@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 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).