mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 00/33] tracing: More updates for 4.12
Date: Fri, 21 Apr 2017 17:30:20 -0400	[thread overview]
Message-ID: <20170421213020.875637678@goodmis.org> (raw)

The biggest change is the rewrite of the function probe trigger code.
I need to make a few enhancements on that code and it was basically
created with a hack on top of an hack, and I didn't want to add more
hacks. Instead, I gutted it and rewrote it in a way that the patch series
is still bisectable. Now the probe triggers can be unique to a tracing
instance. You can add stacktrace to a function within a tracing instance,
or just stop a tracing instance from tracing.


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: dcc19d28091a86d5baf78e3fbb32e3fc3de524be


Namhyung Kim (2):
      ftrace: Add 'function-fork' trace option
      selftests: ftrace: Add -l/--logdir option

Steven Rostedt (VMware) (31):
      ftrace: Fix removing of second function probe
      ftrace: Fix indexing of t_hash_start() from t_next()
      tracing: Have the trace_event benchmark thread call cond_resched_rcu_qs()
      selftests: ftrace: Add a way to reset triggers in the set_ftrace_filter file
      selftests: ftrace: Add a selftest to test event enable/disable func trigger
      selftests: ftrace: Add a test to test function triggers to start and stop tracing
      selftests: ftrace: Add test to test reading of set_ftrace_file
      ftrace: Move the probe function into the tracing directory
      ftrace: Move the function commands into the tracing directory
      ftrace: Remove unused "flags" field from struct ftrace_func_probe
      ftrace: Pass probe ops to probe function
      ftrace: Added ftrace_func_mapper for function probe triggers
      tracing: Have the snapshot trigger use the mapping helper functions
      ftrace: Convert the rest of the function trigger over to the mapping functions
      ftrace: Remove unused unregister_ftrace_function_probe() function
      ftrace: Remove unused unregister_ftrace_function_probe_all() function
      ftrace: Remove printing of data in showing of a function probe
      ftrace: Remove data field from ftrace_func_probe structure
      ftrace: Add helper function ftrace_hash_move_and_update_ops()
      ftrace: Have unregister_ftrace_function_probe_func() return a value
      ftrace: Have each function probe use its own ftrace_ops
      ftrace: Have the function probes call their own function
      ftrace: If the hash for a probe fails to update then free what was initialized
      tracing: Have the trace_array hold the list of registered func probes
      tracing: Pass the trace_array into ftrace_probe_ops functions
      ftrace: Dynamically create the probe ftrace_ops for the trace_array
      tracing/ftrace: Add a better way to pass data via the probe functions
      tracing/ftrace: Allow instances to have their own function probes
      tracing/ftrace: Enable snapshot function trigger to work with instances
      tracing/ftrace: Allow for the traceonoff probe be unique to instances
      tracing/ftrace: Allow for instances to trigger their own stacktrace probes

----
 include/linux/ftrace.h                             |  47 +-
 kernel/trace/ftrace.c                              | 832 +++++++++++++--------
 kernel/trace/trace.c                               | 133 +++-
 kernel/trace/trace.h                               |  75 +-
 kernel/trace/trace_benchmark.c                     |  14 +-
 kernel/trace/trace_events.c                        | 151 ++--
 kernel/trace/trace_functions.c                     | 224 ++++--
 tools/testing/selftests/ftrace/ftracetest          |   5 +
 .../ftrace/test.d/ftrace/func_event_triggers.tc    | 113 +++
 .../ftrace/test.d/ftrace/func_set_ftrace_file.tc   | 132 ++++
 .../test.d/ftrace/func_traceonoff_triggers.tc      | 171 +++++
 tools/testing/selftests/ftrace/test.d/functions    |  21 +
 12 files changed, 1410 insertions(+), 508 deletions(-)
 create mode 100644 tools/testing/selftests/ftrace/test.d/ftrace/func_event_triggers.tc
 create mode 100644 tools/testing/selftests/ftrace/test.d/ftrace/func_set_ftrace_file.tc
 create mode 100644 tools/testing/selftests/ftrace/test.d/ftrace/func_traceonoff_triggers.tc

             reply	other threads:[~2017-04-21 21:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 21:30 Steven Rostedt [this message]
2017-04-21 21:30 ` [for-next][PATCH 01/33] ftrace: Fix removing of second function probe Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 02/33] ftrace: Fix indexing of t_hash_start() from t_next() Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 03/33] tracing: Have the trace_event benchmark thread call cond_resched_rcu_qs() Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 04/33] ftrace: Add function-fork trace option Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 05/33] selftests: ftrace: Add -l/--logdir option Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 06/33] selftests: ftrace: Add a way to reset triggers in the set_ftrace_filter file Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 07/33] selftests: ftrace: Add a selftest to test event enable/disable func trigger Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 08/33] selftests: ftrace: Add a test to test function triggers to start and stop tracing Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 09/33] selftests: ftrace: Add test to test reading of set_ftrace_file Steven Rostedt
2017-05-22  3:23   ` Masami Hiramatsu
2017-05-26 15:02     ` Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 10/33] ftrace: Move the probe function into the tracing directory Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 11/33] ftrace: Move the function commands " Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 12/33] ftrace: Remove unused "flags" field from struct ftrace_func_probe Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 13/33] ftrace: Pass probe ops to probe function Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 14/33] ftrace: Added ftrace_func_mapper for function probe triggers Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 15/33] tracing: Have the snapshot trigger use the mapping helper functions Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 16/33] ftrace: Convert the rest of the function trigger over to the mapping functions Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 17/33] ftrace: Remove unused unregister_ftrace_function_probe() function Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 18/33] ftrace: Remove unused unregister_ftrace_function_probe_all() function Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 19/33] ftrace: Remove printing of data in showing of a function probe Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 20/33] ftrace: Remove data field from ftrace_func_probe structure Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 21/33] ftrace: Add helper function ftrace_hash_move_and_update_ops() Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 22/33] ftrace: Have unregister_ftrace_function_probe_func() return a value Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 23/33] ftrace: Have each function probe use its own ftrace_ops Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 24/33] ftrace: Have the function probes call their own function Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 25/33] ftrace: If the hash for a probe fails to update then free what was initialized Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 26/33] tracing: Have the trace_array hold the list of registered func probes Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 27/33] tracing: Pass the trace_array into ftrace_probe_ops functions Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 28/33] ftrace: Dynamically create the probe ftrace_ops for the trace_array Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 29/33] tracing/ftrace: Add a better way to pass data via the probe functions Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 30/33] tracing/ftrace: Allow instances to have their own function probes Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 31/33] tracing/ftrace: Enable snapshot function trigger to work with instances Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 32/33] tracing/ftrace: Allow for the traceonoff probe be unique to instances Steven Rostedt
2017-04-21 21:30 ` [for-next][PATCH 33/33] tracing/ftrace: Allow for instances to trigger their own stacktrace probes Steven Rostedt

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=20170421213020.875637678@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    /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

Powered by JetHome