|
@@ -41,7 +41,8 @@ OPTIONS
|
|
|
|
|
|
-d::
|
|
|
--del=::
|
|
|
- Delete a probe event.
|
|
|
+ Delete probe events. This accepts glob wildcards('*', '?') and character
|
|
|
+ classes(e.g. [a-z], [!A-Z]).
|
|
|
|
|
|
-l::
|
|
|
--list::
|
|
@@ -50,7 +51,11 @@ OPTIONS
|
|
|
-L::
|
|
|
--line=::
|
|
|
Show source code lines which can be probed. This needs an argument
|
|
|
- which specifies a range of the source code.
|
|
|
+ which specifies a range of the source code. (see LINE SYNTAX for detail)
|
|
|
+
|
|
|
+-f::
|
|
|
+--force::
|
|
|
+ Forcibly add events with existing name.
|
|
|
|
|
|
PROBE SYNTAX
|
|
|
------------
|
|
@@ -76,6 +81,25 @@ and 'ALN2' is end line number in the file. It is also possible to specify how
|
|
|
many lines to show by using 'NUM'.
|
|
|
So, "source.c:100-120" shows lines between 100th to l20th in source.c file. And "func:10+20" shows 20 lines from 10th line of func function.
|
|
|
|
|
|
+EXAMPLES
|
|
|
+--------
|
|
|
+Display which lines in schedule() can be probed:
|
|
|
+
|
|
|
+ ./perf probe --line schedule
|
|
|
+
|
|
|
+Add a probe on schedule() function 12th line with recording cpu local variable:
|
|
|
+
|
|
|
+ ./perf probe schedule:12 cpu
|
|
|
+ or
|
|
|
+ ./perf probe --add='schedule:12 cpu'
|
|
|
+
|
|
|
+ this will add one or more probes which has the name start with "schedule".
|
|
|
+
|
|
|
+Delete all probes on schedule().
|
|
|
+
|
|
|
+ ./perf probe --del='schedule*'
|
|
|
+
|
|
|
+
|
|
|
SEE ALSO
|
|
|
--------
|
|
|
linkperf:perf-trace[1], linkperf:perf-record[1]
|