From: Andi Kleen <andi@firstfloor.org>
To: Luke Gorrie <luke@snabb.co>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: First time user, problem with toplev.py levels (-l)
Date: Wed, 25 Sep 2013 08:24:45 -0700 [thread overview]
Message-ID: <87ob7gsz42.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <CAA2XHbcy6qSvm_s=XPdp3GuXHgTAQqtiDZ1cgvM5rZMF9f00RQ@mail.gmail.com> (Luke Gorrie's message of "Wed, 25 Sep 2013 13:44:41 +0200")
Luke Gorrie <luke@snabb.co> writes:
> I'm a first-time user of toplev.py today. The -l option isn't working
> for me, and I'm wondering if someone can help me understand why?
>
> I've tested with a few different programs under test and combinations
> of -l<n>, -v, and -d. No luck yet. Here's an example below:
What CPU do you have (head -n20 /proc/cpuinfo) ?
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-09-25 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 11:44 First time user, problem with toplev.py levels (-l) Luke Gorrie
2013-09-25 15:24 ` Andi Kleen [this message]
2013-09-25 15:29 ` Luke Gorrie
2013-09-25 15:54 ` Andi Kleen
2013-09-25 17:18 ` Luke Gorrie
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=87ob7gsz42.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=luke@snabb.co \
/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