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/10] tracing: More updates for 5.5
Date: Sat, 23 Nov 2019 13:11:57 -0500 [thread overview]
Message-ID: <20191123181157.851427201@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 16c0f03f629a89e6a1249497202b2c154ff46206
Alexei Starovoitov (1):
ftrace: Return ENOTSUPP when DYNAMIC_FTRACE_WITH_DIRECT_CALLS is not configured
Divya Indi (2):
tracing: Adding new functions for kernel access to Ftrace instances
tracing: Sample module to demonstrate kernel access to Ftrace instances.
Enrico Weigelt, metux IT consult (1):
ftrace: Use BIT() macro
Hassan Naveed (2):
tracing: Use xarray for syscall trace events
tracing: Enable syscall optimization for MIPS
Krzysztof Kozlowski (1):
tracing: Fix Kconfig indentation
Steven Rostedt (VMware) (2):
ftrace: Add a helper function to modify_ftrace_direct() to allow arch optimization
ftrace: Rename ftrace_graph_stub to ftrace_stub_graph
Xianting Tian (1):
ring-buffer: Fix typos in function ring_buffer_producer
----
arch/Kconfig | 8 +++
arch/mips/Kconfig | 1 +
include/asm-generic/vmlinux.lds.h | 8 +--
include/linux/ftrace.h | 63 +++++++++++------
include/linux/trace.h | 3 +-
include/linux/trace_events.h | 3 +-
kernel/trace/Kconfig | 8 +--
kernel/trace/fgraph.c | 6 +-
kernel/trace/ftrace.c | 120 +++++++++++++++++++++++---------
kernel/trace/ring_buffer_benchmark.c | 4 +-
kernel/trace/trace.c | 96 +++++++++++++++++++------
kernel/trace/trace.h | 1 -
kernel/trace/trace_events.c | 27 +++++++-
kernel/trace/trace_syscalls.c | 32 +++++++--
samples/Kconfig | 7 ++
samples/Makefile | 1 +
samples/ftrace/Makefile | 3 +
samples/ftrace/sample-trace-array.c | 131 +++++++++++++++++++++++++++++++++++
samples/ftrace/sample-trace-array.h | 84 ++++++++++++++++++++++
19 files changed, 507 insertions(+), 99 deletions(-)
create mode 100644 samples/ftrace/sample-trace-array.c
create mode 100644 samples/ftrace/sample-trace-array.h
next reply other threads:[~2019-11-23 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 18:11 Steven Rostedt [this message]
2019-11-23 18:11 ` [for-next][PATCH 01/10] ftrace: Add a helper function to modify_ftrace_direct() to allow arch optimization Steven Rostedt
2019-11-23 18:11 ` [for-next][PATCH 02/10] ftrace: Rename ftrace_graph_stub to ftrace_stub_graph Steven Rostedt
2019-11-23 18:12 ` [for-next][PATCH 03/10] ftrace: Return ENOTSUPP when DYNAMIC_FTRACE_WITH_DIRECT_CALLS is not configured Steven Rostedt
2019-11-23 18:12 ` [for-next][PATCH 04/10] ftrace: Use BIT() macro Steven Rostedt
2019-11-23 18:12 ` [for-next][PATCH 05/10] ring-buffer: Fix typos in function ring_buffer_producer Steven Rostedt
2019-11-23 18:12 ` [for-next][PATCH 06/10] tracing: Fix Kconfig indentation Steven Rostedt
2019-11-23 18:12 ` [for-next][PATCH 07/10] tracing: Adding new functions for kernel access to Ftrace instances Steven Rostedt
2019-11-23 18:12 ` [for-next][PATCH 08/10] tracing: Sample module to demonstrate " Steven Rostedt
2019-11-23 18:12 ` [for-next][PATCH 09/10] tracing: Use xarray for syscall trace events Steven Rostedt
2019-11-23 18:12 ` [for-next][PATCH 10/10] tracing: Enable syscall optimization for MIPS 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=20191123181157.851427201@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