public inbox for linux-kernel@vger.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>,
	"Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [for-next][PATCH 0/7] tracing: Add func_no_repeats option
Date: Fri, 16 Apr 2021 13:26:12 -0400	[thread overview]
Message-ID: <20210416172612.086725495@goodmis.org> (raw)

Steven Rostedt (VMware) <rostedt@goodmis.org>, Yordan Karadzhov (VMware) <y.karadz@gmail.com>
  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next

Head SHA1: e1db6338d6fa0d409e45cf20ab5aeaca704f68e7


Steven Rostedt (VMware) (1):
      ftrace: Reuse the output of the function tracer for func_repeats

Yordan Karadzhov (VMware) (6):
      tracing: Define static void trace_print_time()
      tracing: Define new ftrace event "func_repeats"
      tracing: Add "last_func_repeats" to struct trace_array
      tracing: Add method for recording "func_repeats" events
      tracing: Unify the logic for function tracing options
      tracing: Add "func_no_repeats" option for function tracing

----
 kernel/trace/trace.c           |  35 +++++++
 kernel/trace/trace.h           |  19 ++++
 kernel/trace/trace_entries.h   |  22 ++++
 kernel/trace/trace_functions.c | 223 +++++++++++++++++++++++++++++++++++------
 kernel/trace/trace_output.c    |  91 ++++++++++++++---
 5 files changed, 346 insertions(+), 44 deletions(-)

             reply	other threads:[~2021-04-16 17:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 17:26 Steven Rostedt [this message]
2021-04-16 17:26 ` [for-next][PATCH 1/7] tracing: Define static void trace_print_time() Steven Rostedt
2021-04-16 17:26 ` [for-next][PATCH 2/7] tracing: Define new ftrace event "func_repeats" Steven Rostedt
2021-04-16 17:26 ` [for-next][PATCH 3/7] tracing: Add "last_func_repeats" to struct trace_array Steven Rostedt
2021-04-16 17:26 ` [for-next][PATCH 4/7] tracing: Add method for recording "func_repeats" events Steven Rostedt
2021-04-16 17:26 ` [for-next][PATCH 5/7] tracing: Unify the logic for function tracing options Steven Rostedt
2021-04-16 17:26 ` [for-next][PATCH 6/7] tracing: Add "func_no_repeats" option for function tracing Steven Rostedt
2021-04-16 17:26 ` [for-next][PATCH 7/7] ftrace: Reuse the output of the function tracer for func_repeats 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=20210416172612.086725495@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=y.karadz@gmail.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