All of lore.kernel.org
 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/12] tracing: Updates for 5.12
Date: Wed, 10 Feb 2021 21:09:27 -0500	[thread overview]
Message-ID: <20210211020927.829775774@goodmis.org> (raw)


Jinyang He (1):
      ftrace: Remove unused ftrace_force_update()

Masami Hiramatsu (2):
      kprobes: Warn if the kprobe is reregistered
      tracing/dynevent: Delegate parsing to create function

Steven Rostedt (VMware) (4):
      tracing: Do not create "enable" or "filter" files for ftrace event subsystem
      tracepoints: Remove unnecessary "data_args" macro parameter
      tracepoints: Do not punish non static call users
      tracepoints: Code clean up

Tom Zanussi (5):
      tracing: Rework synthetic event command parsing
      tracing: Update synth command errors
      tracing: Add a backward-compatibility check for synthetic event creation
      selftests/ftrace: Update synthetic event syntax errors
      selftests/ftrace: Add '!event' synthetic event syntax check

----
 include/linux/ftrace.h                             |   2 -
 include/linux/tracepoint.h                         |  54 ++--
 kernel/kprobes.c                                   |  13 +-
 kernel/trace/trace.c                               |  23 +-
 kernel/trace/trace.h                               |   3 +-
 kernel/trace/trace_dynevent.c                      |  35 ++-
 kernel/trace/trace_dynevent.h                      |   4 +-
 kernel/trace/trace_events.c                        |  22 +-
 kernel/trace/trace_events_synth.c                  | 320 +++++++++++++++------
 kernel/trace/trace_kprobe.c                        |  33 ++-
 kernel/trace/trace_probe.c                         |  17 ++
 kernel/trace/trace_probe.h                         |   1 +
 kernel/trace/trace_uprobe.c                        |  17 +-
 kernel/tracepoint.c                                |  91 +++---
 .../inter-event/trigger-synthetic-event-syntax.tc  |   4 +
 .../trigger-synthetic_event_syntax_errors.tc       |  35 ++-
 16 files changed, 413 insertions(+), 261 deletions(-)

             reply	other threads:[~2021-02-11  2:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11  2:09 Steven Rostedt [this message]
2021-02-11  2:09 ` [for-next][PATCH 01/12] tracing: Do not create "enable" or "filter" files for ftrace event subsystem Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 02/12] tracepoints: Remove unnecessary "data_args" macro parameter Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 03/12] tracepoints: Do not punish non static call users Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 04/12] tracepoints: Code clean up Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 05/12] ftrace: Remove unused ftrace_force_update() Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 06/12] kprobes: Warn if the kprobe is reregistered Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 07/12] tracing/dynevent: Delegate parsing to create function Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 08/12] tracing: Rework synthetic event command parsing Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 09/12] tracing: Update synth command errors Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 10/12] tracing: Add a backward-compatibility check for synthetic event creation Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 11/12] selftests/ftrace: Update synthetic event syntax errors Steven Rostedt
2021-02-11  2:09 ` [for-next][PATCH 12/12] selftests/ftrace: Add !event synthetic event syntax check 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=20210211020927.829775774@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.