Messages in this thread | | | Date | Fri, 25 Dec 2009 23:06:10 -0500 | From | Masami Hiramatsu <> | Subject | Re: [PATCH] doc: kprobetrace: Add the explanation to remove probe points |
| |
KOSAKI Motohiro wrote: > Latest kprobetrace can remove probe points selectively. thus > documentation should be updated too.
Ah, right.
> > Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Acked-by: Masami Hiramatsu <mhiramat@redhat.com>
Thank you very much!
> Cc: Masami Hiramatsu <mhiramat@redhat.com> > --- > Documentation/trace/kprobetrace.txt | 7 +++++++ > 1 files changed, 7 insertions(+), 0 deletions(-) > > diff --git a/Documentation/trace/kprobetrace.txt b/Documentation/trace/kprobetrace.txt > index 2be6e19..8c88930 100644 > --- a/Documentation/trace/kprobetrace.txt > +++ b/Documentation/trace/kprobetrace.txt > @@ -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. >
-- Masami Hiramatsu
Software Engineer Hitachi Computer Products (America), Inc. Software Solutions Division
e-mail: mhiramat@redhat.com
| |