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/17] tracing: Updates for 5.11
Date: Wed, 11 Nov 2020 19:32:44 -0500 [thread overview]
Message-ID: <20201112003244.764326960@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 58954b3be8b7a8a0ebf1ced6fbbab808e8ccc4b6
Alex Shi (1):
ftrace: Remove unused varible 'ret'
Lukas Bulwahn (1):
MAINTAINERS: assign ./fs/tracefs to TRACING
Qiujun Huang (1):
tracing: Fix some typos in comments
Steven Rostedt (VMware) (14):
ftrace: Move the recursion testing into global headers
ftrace: Add ftrace_test_recursion_trylock() helper function
ftrace: Optimize testing what context current is in
pstore/ftrace: Add recursion protection to the ftrace callback
kprobes/ftrace: Add recursion protection to the ftrace callback
livepatch/ftrace: Add recursion protection to the ftrace callback
livepatch: Trigger WARNING if livepatch function fails due to recursion
perf/ftrace: Add recursion protection to the ftrace callback
perf/ftrace: Check for rcu_is_watching() in callback function
ftrace: Reverse what the RECURSION flag means in the ftrace_ops
ftrace: Add recording of functions that caused recursion
fgraph: Make overruns 4 bytes in graph stack structure
ftrace: Clean up the recursion code a bit
ring-buffer: Add recording of ring buffer recursion into recursed_functions
----
Documentation/trace/ftrace-uses.rst | 84 ++++++++----
MAINTAINERS | 1 +
arch/csky/kernel/probes/ftrace.c | 12 +-
arch/parisc/kernel/ftrace.c | 16 ++-
arch/powerpc/kernel/kprobes-ftrace.c | 11 +-
arch/s390/kernel/ftrace.c | 16 ++-
arch/x86/kernel/kprobes/ftrace.c | 12 +-
fs/pstore/ftrace.c | 6 +
include/linux/ftrace.h | 17 +--
include/linux/trace_recursion.h | 232 +++++++++++++++++++++++++++++++++
kernel/livepatch/patch.c | 5 +
kernel/trace/Kconfig | 39 ++++++
kernel/trace/Makefile | 1 +
kernel/trace/blktrace.c | 4 +-
kernel/trace/bpf_trace.c | 2 +-
kernel/trace/fgraph.c | 3 +-
kernel/trace/ftrace.c | 30 ++---
kernel/trace/ring_buffer.c | 12 +-
kernel/trace/trace.c | 2 +-
kernel/trace/trace.h | 177 -------------------------
kernel/trace/trace_benchmark.c | 6 +-
kernel/trace/trace_dynevent.c | 2 +-
kernel/trace/trace_dynevent.h | 6 +-
kernel/trace/trace_entries.h | 6 +-
kernel/trace/trace_event_perf.c | 13 +-
kernel/trace/trace_events.c | 5 +-
kernel/trace/trace_events_filter.c | 2 +-
kernel/trace/trace_events_hist.c | 2 +-
kernel/trace/trace_events_synth.c | 4 +-
kernel/trace/trace_export.c | 2 +-
kernel/trace/trace_functions.c | 14 +-
kernel/trace/trace_functions_graph.c | 2 +-
kernel/trace/trace_hwlat.c | 4 +-
kernel/trace/trace_output.c | 6 +-
kernel/trace/trace_output.h | 1 +
kernel/trace/trace_recursion_record.c | 236 ++++++++++++++++++++++++++++++++++
kernel/trace/trace_selftest.c | 7 +-
kernel/trace/trace_stack.c | 1 -
kernel/trace/tracing_map.c | 6 +-
kernel/trace/tracing_map.h | 2 +-
40 files changed, 723 insertions(+), 286 deletions(-)
create mode 100644 include/linux/trace_recursion.h
create mode 100644 kernel/trace/trace_recursion_record.c
next reply other threads:[~2020-11-12 1:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 0:32 Steven Rostedt [this message]
2020-11-12 0:32 ` [for-next][PATCH 01/17] ftrace: Move the recursion testing into global headers Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 02/17] ftrace: Add ftrace_test_recursion_trylock() helper function Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 03/17] ftrace: Optimize testing what context current is in Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 04/17] pstore/ftrace: Add recursion protection to the ftrace callback Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 05/17] kprobes/ftrace: " Steven Rostedt
2020-11-12 0:32 ` Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 06/17] livepatch/ftrace: " Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 07/17] livepatch: Trigger WARNING if livepatch function fails due to recursion Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 08/17] perf/ftrace: Add recursion protection to the ftrace callback Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 09/17] perf/ftrace: Check for rcu_is_watching() in callback function Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 10/17] ftrace: Reverse what the RECURSION flag means in the ftrace_ops Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 11/17] ftrace: Add recording of functions that caused recursion Steven Rostedt
2020-11-12 0:32 ` Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 12/17] fgraph: Make overruns 4 bytes in graph stack structure Steven Rostedt
2020-11-12 9:18 ` David Laight
2020-11-12 14:39 ` Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 13/17] ftrace: Clean up the recursion code a bit Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 14/17] ring-buffer: Add recording of ring buffer recursion into recursed_functions Steven Rostedt
2020-11-12 0:32 ` [for-next][PATCH 15/17] ftrace: Remove unused varible ret Steven Rostedt
2020-11-12 0:33 ` [for-next][PATCH 16/17] tracing: Fix some typos in comments Steven Rostedt
2020-11-12 0:33 ` [for-next][PATCH 17/17] MAINTAINERS: assign ./fs/tracefs to TRACING 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=20201112003244.764326960@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.