Messages in this thread | | | Subject | Re: [PATCH 7/7] ftrace, perf: Add filter support for function trace event | From | Steven Rostedt <> | Date | Mon, 16 Jan 2012 18:59:08 -0500 |
| |
On Mon, 2012-01-02 at 10:04 +0100, Jiri Olsa wrote: > Adding support to filter function trace event via perf > interface. It is now possible to use filter interface > in the perf tool like: > > perf record -e ftrace:function --filter="(ip == mm_*)" ls > > The filter syntax is restricted to the the 'ip' field only, > and following operators are accepted '==' '!=' '||', ending > up with the filter strings like: > > ip == f1[, ]f2 ... || ip != f3[, ]f4 ... > > with comma ',' or space ' ' as a function separator. If the > space ' ' is used as a separator, the right side of the > assignment needs to be enclosed in double quotes '"'. > > The '==' operator adds trace filter with same effect as would > be added via set_ftrace_filter file. > > The '!=' operator adds trace filter with same effect as would > be added via set_ftrace_notrace file. > > The right side of the '!=', '==' operators is list of functions > or regexp. to be added to filter separated by space. > > The '||' operator is used for connecting multiple filter definitions > together. It is possible to have more than one '==' and '!=' > operators within one filter string.
Hate to ask you this, but can you rebase this patch against latest tip/perf/core? Things have changed that cause this patch not to apply.
I'll go ahead and test your other 6 patches.
Thanks!
-- Steve
| |