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 14:35:33 -0600	[thread overview]
Message-ID: <CAJLXCZTN1xLXk79kh5i8WbJBB+4sh0Qs1v+PndhLKSrPPvZ2wQ@mail.gmail.com> (raw)
In-Reply-To: <CAJLXCZTzRdLYmcRVTO_AeRawmZ55AtdABcKpu5T5A-Z89iHnbA@mail.gmail.com>

On Fri, May 31, 2013 at 1:09 AM, Andrew Davidoff <davidoff@qedmf.net> wrote:
> 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.

After struggling a bit more with this on the original host:

Ubuntu 10.04.4 LTS
kernel 2.6.32-47-server
perf versions 3.9.4 and 3.8.13

with no change in results, I gave it a shot on a CentOS 6 virtual
machine on my Mac:

CentOS release 6.4 (Final)
kernel 3.9.4 AND kernel 2.6.32-358.2.1.el6.x86_64
perf version 3.9.4

And perf record is working as I'd expect it to. To be clear about the
description above, under CentOS,  perf record 3.9.4 is recording
samples whether I'm running kernel 3.9.4 or 2.6.32-358.2.1.el6.x86_64.

So...Ubuntu thing? Or maybe just a 10.04 thing (yeah, I know it's old).

Maybe this'll help someone.

Thanks all.
Andy

  reply	other threads:[~2013-05-31 20:35 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 [this message]
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=CAJLXCZTN1xLXk79kh5i8WbJBB+4sh0Qs1v+PndhLKSrPPvZ2wQ@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.