From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-trace-users@vger.kernel.org,
linux-kselftest@vger.kernel.org, shuah@kernel.org,
Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Subject: Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features
Date: Fri, 22 Jun 2018 15:04:12 +0900 [thread overview]
Message-ID: <20180622150412.ef26a31acb46c5baebd97ddb@kernel.org> (raw)
In-Reply-To: <20180621161648.29e7a4cc@gandalf.local.home>
Hi Steve,
On Thu, 21 Jun 2018 16:16:48 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> Hi Masami,
>
> Are you going to post another version of this patch set?
No, this is the latest one which I sent to LKML.
Oops, it was 2 month ago now...
Thank you,
>
> -- Steve
>
>
> On Wed, 25 Apr 2018 21:16:06 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > Hi,
> >
> > This is the 7th version of the fetch-arg improvement series.
> > This includes variable changes on fetcharg framework like,
> >
> > - Add fetcharg testcases (syntax, argN, symbol, string and array)
> > and probepoint testcase.
> > - Rewrite fetcharg framework with fetch_insn, switch-case based
> > instead of function pointer.
> > - Add "symbol" type support, which shows symbol+offset instead of
> > address value.
> > - Add "$argN" fetcharg, which fetches function parameters.
> > (currently only for x86-64)
> > - Add array type support (including string arrary :) ) ,
> > which enables to get fixed length array from probe-events.
> > - Add array type support for perf-probe, so that user can
> > dump partial array entries.
> >
> > V6 is here:
> > https://lkml.org/lkml/2018/3/17/75
> >
> > Changes from the v6 are here:
> > [6/16] - Fix to return an error if failed to fetch string and
> > fill zero-length data_loc in error case.
> > [11/16] - Update document for restructured text.
> > [15/16] - Fix README test.
> > [16/16] - Add type-casting description (and note) to documentation.
> >
> > And rebased on the latest Steve's ftrace/core branch.
> >
> > Thank you,
> >
> > ---
> >
> > Masami Hiramatsu (16):
> > tracing: probeevent: Cleanup print argument functions
> > tracing: probeevent: Cleanup argument field definition
> > tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions
> > tracing: probeevent: Introduce new argument fetching code
> > tracing: probeevent: Unify fetch type tables
> > tracing: probeevent: Return consumed bytes of dynamic area
> > tracing: probeevent: Append traceprobe_ for exported function
> > tracing: probeevent: Unify fetch_insn processing common part
> > tracing: probeevent: Add symbol type
> > x86: ptrace: Add function argument access API
> > tracing: probeevent: Add $argN for accessing function args
> > tracing: probeevent: Add array type support
> > selftests: ftrace: Add a testcase for symbol type
> > selftests: ftrace: Add a testcase for $argN with kprobe_event
> > selftests: ftrace: Add a testcase for array type with kprobe_event
> > perf-probe: Add array argument support
> >
> >
> > Documentation/trace/kprobetrace.rst | 23 +
> > arch/Kconfig | 7
> > arch/x86/Kconfig | 1
> > arch/x86/include/asm/ptrace.h | 38 +
> > kernel/trace/trace.c | 9
> > kernel/trace/trace_kprobe.c | 358 ++++--------
> > kernel/trace/trace_probe.c | 620 +++++++++-----------
> > kernel/trace/trace_probe.h | 282 +++------
> > kernel/trace/trace_probe_tmpl.h | 216 +++++++
> > kernel/trace/trace_uprobe.c | 176 ++----
> > tools/perf/Documentation/perf-probe.txt | 12
> > tools/perf/util/probe-event.c | 20 +
> > tools/perf/util/probe-event.h | 2
> > tools/perf/util/probe-file.c | 5
> > tools/perf/util/probe-file.h | 1
> > tools/perf/util/probe-finder.c | 95 ++-
> > .../ftrace/test.d/kprobe/kprobe_args_argN.tc | 25 +
> > .../ftrace/test.d/kprobe/kprobe_args_array.tc | 92 +++
> > .../ftrace/test.d/kprobe/kprobe_args_symbol.tc | 77 ++
> > 19 files changed, 1127 insertions(+), 932 deletions(-)
> > create mode 100644 kernel/trace/trace_probe_tmpl.h
> > create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_argN.tc
> > create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_array.tc
> > create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_symbol.tc
> >
> > --
> > Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
>
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2018-06-22 6:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 12:16 [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features Masami Hiramatsu
2018-04-25 12:16 ` [PATCH v7 01/16] tracing: probeevent: Cleanup print argument functions Masami Hiramatsu
2018-04-25 12:17 ` [PATCH v7 02/16] tracing: probeevent: Cleanup argument field definition Masami Hiramatsu
2018-04-25 12:17 ` [PATCH v7 03/16] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions Masami Hiramatsu
2018-04-25 12:18 ` [PATCH v7 04/16] tracing: probeevent: Introduce new argument fetching code Masami Hiramatsu
2018-04-25 12:18 ` [PATCH v7 05/16] tracing: probeevent: Unify fetch type tables Masami Hiramatsu
2018-04-25 12:19 ` [PATCH v7 06/16] tracing: probeevent: Return consumed bytes of dynamic area Masami Hiramatsu
2018-04-25 12:19 ` [PATCH v7 07/16] tracing: probeevent: Append traceprobe_ for exported function Masami Hiramatsu
2018-04-25 12:19 ` [PATCH v7 08/16] tracing: probeevent: Unify fetch_insn processing common part Masami Hiramatsu
2018-04-25 12:20 ` [PATCH v7 09/16] tracing: probeevent: Add symbol type Masami Hiramatsu
2018-04-25 12:20 ` [PATCH v7 10/16] x86: ptrace: Add function argument access API Masami Hiramatsu
2018-04-25 12:21 ` [PATCH v7 11/16] tracing: probeevent: Add $argN for accessing function args Masami Hiramatsu
2018-04-25 12:21 ` [PATCH v7 12/16] tracing: probeevent: Add array type support Masami Hiramatsu
2018-04-25 12:22 ` [PATCH v7 13/16] selftests: ftrace: Add a testcase for symbol type Masami Hiramatsu
2018-04-25 12:22 ` [PATCH v7 14/16] selftests: ftrace: Add a testcase for $argN with kprobe_event Masami Hiramatsu
2018-04-25 12:23 ` [PATCH v7 15/16] selftests: ftrace: Add a testcase for array type " Masami Hiramatsu
2018-04-25 12:23 ` [PATCH v7 16/16] perf-probe: Add array argument support Masami Hiramatsu
2018-04-27 1:42 ` [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features Steven Rostedt
2018-05-03 22:11 ` Steven Rostedt
2018-05-04 15:48 ` Masami Hiramatsu
2018-05-04 16:06 ` Steven Rostedt
2018-05-04 17:30 ` Naveen N. Rao
2018-05-05 2:38 ` Masami Hiramatsu
2018-05-05 7:46 ` Naveen N. Rao
2018-05-05 14:32 ` Masami Hiramatsu
2018-05-07 8:11 ` Naveen N. Rao
2018-05-07 14:53 ` Masami Hiramatsu
2018-05-08 10:11 ` Naveen N. Rao
2018-05-08 15:02 ` Masami Hiramatsu
2018-05-08 18:01 ` Naveen N. Rao
2018-05-05 15:51 ` Masami Hiramatsu
2018-05-07 15:30 ` Steven Rostedt
2018-05-08 4:01 ` Masami Hiramatsu
2018-05-07 15:21 ` Steven Rostedt
2018-06-21 20:16 ` Steven Rostedt
2018-06-22 6:04 ` Masami Hiramatsu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180622150412.ef26a31acb46c5baebd97ddb@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tom.zanussi@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox