[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3wrm87ba7.fsf@gmail.com>
Date: Thu, 13 Jan 2011 22:18:24 +0100
From: Franck Bui-Huu <vagabon.xyz@...il.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc: Arnaldo Carvalho de Melo <acme@...hat.com>,
Ingo Molnar <mingo@...e.hu>,
Steven Rostedt <rostedt@...dmis.org>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, 2nddept-manager@....hitachi.co.jp,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Chase Douglas <chase.douglas@...onical.com>
Subject: Re: [PATCH -perf/perf/core 5/6] perf probe: Add variable filter support
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> writes:
> Add filters support for available variable list.
> Default filter is "!__k???tab_*&!__crc_*" for
> filtering out automatically generated symbols.
>
> The format of filter rule is "[!]GLOBPATTERN", so
> you can use wild cards. If the filter rule starts with
> '!', matched variables are filter out.
>
> e.g.)
> # perf probe -V schedule --externs --filter=cpu*
I'm wondering if the different syntax below could be simpler:
$ perf probe add <probe>
$ perf probe del <probe>
$ perf probe show
$ perf probe list <line>
... --vars[=<pattern>] [--externs] <probe>
... --funcs[=<pattern>]
instead of respectively:
$ perf probe --add=<probe>
$ perf probe --del=<probe>
$ perf probe [--list|-l]
$ perf probe [--line|-L] <line>
$ perf probe -V <probe> [--externs] [--filter=<pattern>]
$ perf probe --funcs
--
Franck
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists