[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180507112154.5c1ea44c@gandalf.local.home>
Date: Mon, 7 May 2018 11:21:54 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Tom Zanussi <tom.zanussi@...ux.intel.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-trace-users@...r.kernel.org, linux-kselftest@...r.kernel.org,
shuah@...nel.org, Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>
Subject: Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
On Sat, 5 May 2018 11:38:03 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:
> On Fri, 4 May 2018 12:06:42 -0400
> Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > On Sat, 5 May 2018 00:48:28 +0900
> > Masami Hiramatsu <mhiramat@...nel.org> wrote:
> >
> > > So the syntax will be
> > >
> > > p[:EVENT] SYM[(CAST)|+OFFS] [FETCHARG]
> > >
> > > And here is an example;
> > >
> > > p:myevent vfs_read(void *file, char *buf, size_t count, void *pos) $arg1 $arg2
> >
> > If we do this, why bother with $arg1 $arg2?
>
> User may want to trace only some of them. :)
Yes, and this is why I like my solution of the NULL parameter, and you
don't need to show anything after what you want.
p:myevent vfs_read(void *file, NULL, size_t count)
would only trace file and count, and ignore buf and pos.
-- Steve
Powered by blists - more mailing lists