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/11] tracing: More updates for 5.17
Date: Sat, 11 Dec 2021 20:26:17 -0500	[thread overview]
Message-ID: <20211212012617.690710310@goodmis.org> (raw)

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

Head SHA1: 85c62c8c3749eec02ba81217bdcac26867dc262e


Beau Belgrave (1):
      tracing: Do not let synth_events block other dyn_event systems during create

Jiri Olsa (1):
      tracing: Iterate trace_[ku]probe objects directly

John Keeping (1):
      tracing: Make trace_marker{,_raw} stream-like

Steven Rostedt (VMware) (2):
      tracefs: Use d_inode() helper function to get the dentry inode
      tracing: Use trace_iterator_reset() in tracing_read_pipe()

Tom Zanussi (4):
      tracing: Change event_command func() to parse()
      tracing: Change event_trigger_ops func() to trigger()
      tracing: Add helper functions to simplify event_command.parse() callback handling
      tracing: Have existing event_command.parse() implementations use helpers

Xiu Jianfeng (1):
      tracing: Use memset_startat helper in trace_iterator_reset()

Yinan Liu (1):
      script/sorttable: Code style improvements

----
 fs/tracefs/inode.c                  |  24 +-
 kernel/trace/trace.c                |  21 +-
 kernel/trace/trace.h                |  72 +++--
 kernel/trace/trace_eprobe.c         |  11 +-
 kernel/trace/trace_events_hist.c    | 109 +++----
 kernel/trace/trace_events_synth.c   |  13 +-
 kernel/trace/trace_events_trigger.c | 558 ++++++++++++++++++++++++++----------
 kernel/trace/trace_kprobe.c         |  13 +-
 kernel/trace/trace_uprobe.c         |  23 +-
 scripts/sorttable.h                 |   4 +-
 10 files changed, 558 insertions(+), 290 deletions(-)

             reply	other threads:[~2021-12-12  1:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12  1:26 Steven Rostedt [this message]
2021-12-12  1:26 ` [for-next][PATCH 01/11] tracing: Make trace_marker{,_raw} stream-like Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 02/11] script/sorttable: Code style improvements Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 03/11] tracefs: Use d_inode() helper function to get the dentry inode Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 04/11] tracing: Iterate trace_[ku]probe objects directly Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 05/11] tracing: Do not let synth_events block other dyn_event systems during create Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 06/11] tracing: Use memset_startat helper in trace_iterator_reset() Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 07/11] tracing: Use trace_iterator_reset() in tracing_read_pipe() Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 08/11] tracing: Change event_command func() to parse() Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 09/11] tracing: Change event_trigger_ops func() to trigger() Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 10/11] tracing: Add helper functions to simplify event_command.parse() callback handling Steven Rostedt
2021-12-12  1:26 ` [for-next][PATCH 11/11] tracing: Have existing event_command.parse() implementations use helpers 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=20211212012617.690710310@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

all inboxes | Powered by JetHome®