[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160224133428.GE24505@kernel.org>
Date: Wed, 24 Feb 2016 10:34:28 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Jiri Olsa <jolsa@...nel.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Stephane Eranian <eranian@...gle.com>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 13/15] perf script: Display data_src values
Em Wed, Feb 24, 2016 at 09:46:54AM +0100, Jiri Olsa escreveu:
> Adding support to display data_src values,
> for events with data_src data in sample.
While testing patches in this series I noticed this:
[root@...et ~]# perf mem record -a
Error: unknown switch `a'
Usage: perf mem record [<options>] [<command>]
or: perf mem record [<options>] -- <command> [<options>]
-e, --event <event> event selector. use 'perf mem record -e list' to list available events
-v, --verbose be more verbose (show counter open errors, etc)
[root@...et ~]# perf mem record -- -a
^C[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 3.149 MB perf.data (173 samples) ]
[root@...et ~]#
Can't we imply the -- after 'record', i.e pass everything after 'record'
to the underlying 'perf record' call?
- Arnaldo
Powered by blists - more mailing lists