From: Frederic Weisbecker <fweisbec@gmail.com>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Possible problem with perf tool
Date: Thu, 2 Jul 2009 02:11:23 +0200 [thread overview]
Message-ID: <20090702001122.GB5025@nowhere> (raw)
In-Reply-To: <4A4BF968.3060505@gmail.com>
On Wed, Jul 01, 2009 at 09:03:52PM -0300, Kevin Winchester wrote:
>
> I was playing with perf to get an idea of what it can do, so I started with a basic test:
>
> $ perf stat ls
> CREDITS PERF-BUILD-OPTIONS builtin-annotate.c builtin-help.o builtin-record.c builtin-report.o builtin-top.c command-list.txt libperf.a perf.h
> Documentation PERF-CFLAGS builtin-annotate.o builtin-list.c builtin-record.o builtin-stat.c builtin-top.o common-cmds.h perf perf.o
> Makefile PERF-VERSION-FILE builtin-help.c builtin-list.o builtin-report.c builtin-stat.o builtin.h design.txt perf.c util
>
> Performance counter stats for 'ls':
>
> 1.675774 task-clock-msecs # 0.772 CPUs
> 13 context-switches # 0.008 M/sec
> 0 CPU-migrations # 0.000 M/sec
> 212 page-faults # 0.127 M/sec
> 2925124 cycles # 1745.536 M/sec
> 1048640 instructions # 0.358 IPC
> 547552 cache-references # 326.746 M/sec
> 8455 cache-misses # 5.045 M/sec
>
> 0.002170123 seconds time elapsed
>
>
>
>
> Looks good, so I tried:
>
> $ perf stat ls -l
> Error: unknown switch `l'
>
>
>
>
> So I tried instead:
>
> $ perf stat 'ls -l'
> ls -l: No such file or directory
>
> Performance counter stats for 'ls -l':
>
> <not counted> task-clock-msecs
> <not counted> context-switches
> <not counted> CPU-migrations
> <not counted> page-faults
> <not counted> cycles
> <not counted> instructions
> <not counted> cache-references
> <not counted> cache-misses
>
> 0.000594919 seconds time elapsed
>
>
>
>
>
> Am I doing something wrong here? Or perhaps perf should be taught the difference between command-line switches before or after the perf command (e.g. stat) being invoked?
>
Hi,
When you have a command line to play that has parameters, then
separate the perf parameters from the command line using "--":
./perf stat -- ls -l
I guess it's inspired from the when you have to pass paths
and branches at the same time:
git-diff branch1 branch2 -- kernel/perf_counter.c
prev parent reply other threads:[~2009-07-02 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 0:03 Possible problem with perf tool Kevin Winchester
2009-07-02 0:11 ` Frederic Weisbecker [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=20090702001122.GB5025@nowhere \
--to=fweisbec@gmail.com \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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