summaryrefslogtreecommitdiff
path: root/Documentation/trace
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>2013-06-17 10:59:17 -0400
committerSteven Rostedt <rostedt@goodmis.org>2013-06-19 23:32:06 -0400
commitc3e13c7c0605677a2c94957b39157f4501cea9a8 (patch)
treecff1b8e71ea263b161e296a08598cc34d831b80a /Documentation/trace
parent1a891cf19cdfb645827969cc6aeaeebdefeb87b2 (diff)
tracing: Update documentation on tracepoint glob matching
b0f1a59a "tracing/filters: Use a different op for glob match" added glob matching to tracepoint filter strings. It uses the ftrace function tracing glob matching facility that allows for the wild card character (*) to be used at the start and/or end of the matching string. But the documentation still states that the filtering only allows for exact string matches. Cc: Li Zefan <lizefan@huawei.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'Documentation/trace')
-rw-r--r--Documentation/trace/events.txt13
1 files changed, 11 insertions, 2 deletions
diff --git a/Documentation/trace/events.txt b/Documentation/trace/events.txt
index 41911240c65c..37732a220d33 100644
--- a/Documentation/trace/events.txt
+++ b/Documentation/trace/events.txt
@@ -187,9 +187,18 @@ The operators available for numeric fields are:
And for string fields they are:
-==, !=
+==, !=, ~
-Currently, only exact string matches are supported.
+The glob (~) only accepts a wild card character (*) at the start and or
+end of the string. For example:
+
+ prev_comm ~ "*sh"
+ prev_comm ~ "sh*"
+ prev_comm ~ "*sh*"
+
+But does not allow for it to be within the string:
+
+ prev_comm ~ "ba*sh" <-- is invalid
5.2 Setting filters
-------------------