kprobetrace: documentation fix
Subsystems (2)
PATCH 1/1 kprobetrace: documentation fix
shell interpret $val is as shell variable. thus we need quote if we use echo command.
Signed-off-by KOSAKI Motohiro <[email protected]>
Cc Masami Hiramatsu <[email protected]>
--- Documentation/trace/kprobetrace.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
Documentation/trace/kprobetrace.txt +2 -2
@@ -82,13 +82,13 @@ Usage examples To add a probe as a new event, write a new definition to kprobe_events as below. - echo p:myprobe do_sys_open dfd=$arg0 filename=$arg1 flags=$arg2 mode=$arg3 > /sys/kernel/debug/tracing/kprobe_events + echo 'p:myprobe do_sys_open dfd=$arg0 filename=$arg1 flags=$arg2 mode=$arg3' > /sys/kernel/debug/tracing/kprobe_events This sets a kprobe on the top of do_sys_open() function with recording 1st to 4th arguments as "myprobe" event. As this example shows, users can choose more familiar names for each arguments. - echo r:myretprobe do_sys_open $retval >> /sys/kernel/debug/tracing/kprobe_events + echo 'r:myretprobe do_sys_open $retval' >> /sys/kernel/debug/tracing/kprobe_events This sets a kretprobe on the return point of do_sys_open() function with recording return value as "myretprobe" event.
Signature · 1 line
1.6.5.2
PATCH 1/1 doc: kprobetrace: Add the explanation to remove probe points
Latest kprobetrace can remove probe points selectively. thus documentation should be updated too.
Signed-off-by KOSAKI Motohiro <[email protected]>
Cc Masami Hiramatsu <[email protected]>
--- Documentation/trace/kprobetrace.txt | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-)
Documentation/trace/kprobetrace.txt +7 -0
@@ -24,6 +24,7 @@ Synopsis of kprobe_events ------------------------- p[:[GRP/]EVENT] SYMBOL[+offs]|MEMADDR [FETCHARGS] : Set a probe r[:[GRP/]EVENT] SYMBOL[+0] [FETCHARGS] : Set a return probe + -:[GRP/]EVENT : Clear a probe GRP : Group name. If omitted, use "kprobes" for it. EVENT : Event name. If omitted, the event name is generated
@@ -121,6 +122,12 @@ print fmt: "(%lx) dfd=%lx filename=%lx flags=%lx mode=%lx", REC->ip, REC->dfd, R This clears all probe points. + Or, + + echo -:myprobe >> kprobe_events + + This clears probe points selectively. + Right after definition, each event is disabled by default. For tracing these events, you need to enable it.
Signature · 1 line
1.6.5.2
Re: [PATCH] doc: kprobetrace: Add the explanation to remove probe points
Quoted 2 lines · KOSAKI Motohiro
Latest kprobetrace can remove probe points selectively. thus documentation should be updated too.
Ah, right.
Quoted 2 lines
Signed-off-by KOSAKI Motohiro <[email protected]>
Acked-by Masami Hiramatsu <[email protected]>
Thank you very much!
Quoted 30 lines
Cc Masami Hiramatsu <[email protected]>--- Documentation/trace/kprobetrace.txt | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-)Documentation/trace/kprobetrace.txt +7
-0@@ -24,6 +24,7 @@ Synopsis of kprobe_events ------------------------- p[:[GRP/]EVENT] SYMBOL[+offs]|MEMADDR [FETCHARGS] : Set a probe r[:[GRP/]EVENT] SYMBOL[+0] [FETCHARGS] : Set a return probe + -:[GRP/]EVENT : Clear a probe GRP : Group name. If omitted, use "kprobes" for it. EVENT : Event name. If omitted, the event name is generated@@ -121,6 +122,12 @@ print fmt: "(%lx) dfd=%lx filename=%lx flags=%lx mode=%lx", REC->ip, REC->dfd, R This clears all probe points. + Or, + + echo -:myprobe >> kprobe_events + + This clears probe points selectively. + Right after definition, each event is disabled by default. For tracing these events, you need to enable it.
Signature · 7 lines
Masami Hiramatsu Software Engineer Hitachi Computer Products (America), Inc. Software Solutions Division e-mail: [email protected]
Quoted 3 lines · KOSAKI Motohiro
shell interpret $val is as shell variable. thus we need quote if we use echo command.
Right.
Thank you for fixing!
Quoted 1 line
Signed-off-by KOSAKI Motohiro <[email protected]>
Acked-by Masami Hiramatsu <[email protected]>
Quoted 24 lines
--- Documentation/trace/kprobetrace.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)Documentation/trace/kprobetrace.txt +2
-2@@ -82,13 +82,13 @@ Usage examples To add a probe as a new event, write a new definition to kprobe_events as below. - echo p:myprobe do_sys_open dfd=$arg0 filename=$arg1 flags=$arg2 mode=$arg3 > /sys/kernel/debug/tracing/kprobe_events + echo 'p:myprobe do_sys_open dfd=$arg0 filename=$arg1 flags=$arg2 mode=$arg3' > /sys/kernel/debug/tracing/kprobe_events This sets a kprobe on the top of do_sys_open() function with recording 1st to 4th arguments as "myprobe" event. As this example shows, users can choose more familiar names for each arguments. - echo r:myretprobe do_sys_open $retval >> /sys/kernel/debug/tracing/kprobe_events + echo 'r:myretprobe do_sys_open $retval' >> /sys/kernel/debug/tracing/kprobe_events This sets a kretprobe on the return point of do_sys_open() function with recording return value as "myretprobe" event.
Signature · 7 lines
Masami Hiramatsu Software Engineer Hitachi Computer Products (America), Inc. Software Solutions Division e-mail: [email protected]