[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191118220304.GE20465@kernel.org>
Date: Mon, 18 Nov 2019 19:03:04 -0300
From: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Ingo Molnar <mingo@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
linux-kernel@...r.kernel.org,
Tom Zanussi <tom.zanussi@...ux.intel.com>,
Ravi Bangoria <ravi.bangoria@...ux.ibm.com>,
Namhyung Kim <namhyung@...nel.org>
Subject: Re: [PATCH v3 4/7] perf probe: Generate event name with line number
Em Mon, Nov 18, 2019 at 05:12:20PM +0900, Masami Hiramatsu escreveu:
> Generate event name from function name with line number
> as <function>_L<line_number>. Note that this is only for
> the new event which is defined by the line number of
> function (except for line 0).
>
> If there is another event on same line, you have to use
> "-f" option. In that case, the new event has "_1" suffix.
>
> e.g.
> # perf probe -a kernel_read:2
> Added new event:
> probe:kernel_read_L2 (on kernel_read:2)
>
> You can now use it in all perf tools, such as:
>
> perf record -e probe:kernel_read_L2 -aR sleep 1
>
>
> But if we omit the line number or 0th line, it will
> have no suffix.
>
> # perf probe -a kernel_read:0
> Added new event:
> probe:kernel_read (on kernel_read)
>
> You can now use it in all perf tools, such as:
>
> perf record -e probe:kernel_read -aR sleep 1
>
> # perf probe -l
> probe:kernel_read (on kernel_read@...ux-5.0.0/fs/read_write.c)
> probe:kernel_read_L2 (on kernel_read:2@...ux-5.0.0/fs/read_write.c)
Thanks, tested and applied.
- Arnaldo
Powered by blists - more mailing lists