From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Jia-Ju Bai <baijiaju1990@gmail.com>,
Jianlin Lv <iecedge@gmail.com>,
Linyu Yuan <quic_linyyuan@quicinc.com>,
Mark Rutland <mark.rutland@arm.com>,
Ross Zwisler <zwisler@chromium.org>,
Song Shuai <suagrfillet@gmail.com>, Tom Rix <trix@redhat.com>,
Tom Zanussi <zanussi@kernel.org>,
Wang ShaoBo <bobo.shaobowang@huawei.com>
Subject: [GIT PULL] tracing: Updates for 6.3
Date: Mon, 20 Feb 2023 15:44:32 -0500 [thread overview]
Message-ID: <20230220154432.12eefbf6@gandalf.local.home> (raw)
Linus,
tracing updates for 6.3:
- Add function names as a way to filter function addresses
- Add sample module to test ftrace ops and dynamic trampolines
- Allow stack traces to be passed from beginning event to end event for
synthetic events. This will allow seeing the stack trace of when a task is
scheduled out and recorded when it gets scheduled back in.
- Add trace event helper __get_buf() to use as a temporary buffer when printing
out trace event output.
- Add kernel command line to create trace instances on boot up.
- Add enabling of events to instances created at boot up.
- Add trace_array_puts() to write into instances.
- Allow boot instances to take a snapshot at the end of boot up.
- Allow live patch modules to include trace events
- Minor fixes and clean ups
Please pull the latest trace-v6.3 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace-v6.3
Tag SHA1: 58d2fb362d449573480ed049e6b9f4b65af8ca0c
Head SHA1: 7568a21e52f60930ba8ae7897c2521bdab3ef5a4
Arnd Bergmann (1):
ftrace: sample: avoid open-coded 64-bit division
Bagas Sanjaya (1):
tracing/histogram: Wrap remaining shell snippets in code blocks
Davidlohr Bueso (1):
tracing/osnoise: No need for schedule_hrtimeout range
Jia-Ju Bai (1):
tracing: Add NULL checks for buffer in ring_buffer_free_read_page()
Jianlin Lv (1):
tracepoint: Allow livepatch module add trace event
Linyu Yuan (1):
tracing: Acquire buffer from temparary trace sequence
Mark Rutland (1):
ftrace: Add sample with custom ops
Ross Zwisler (1):
tracing: Always use canonical ftrace path
Song Shuai (1):
samples: ftrace: Include the nospec-branch.h only for x86
Steven Rostedt (Google) (16):
tracing: Add a way to filter function addresses to function names
tracing/selftests: Add test for event filtering on function name
tracing: Simplify calculating entry size using struct_size()
tracing: Allow stacktraces to be saved as histogram variables
tracing: Allow synthetic events to pass around stacktraces
tracing/histogram: Add stacktrace type
tracing/histogram: Document variable stacktrace
tracing/histogram: Add simple tests for stacktrace usage of synthetic events
perf/tracing: Use stage6 of tracing to not duplicate macros
bpf/tracing: Use stage6 of tracing to not duplicate macros
tracing: Fix trace_event_raw_event_synth() if else statement
tracing: Add creation of instances at boot command line
tracing: Add enabling of events to boot instances
tracing: Add trace_array_puts() to write into instance
tracing: Allow boot instances to have snapshot buffers
tracing: Add BUILD_BUG() to make sure stacktrace fits in strings
Tom Rix (1):
samples: ftrace: Make some global variables static
Tom Zanussi (4):
tracing/histogram: Don't use strlen to find length of stacktrace variables
tracing/histogram: Fix a few problems with stacktrace variable printing
tracing/histogram: Fix stacktrace key
tracing/histogram: Fix stacktrace histogram Documententation
Wang ShaoBo (1):
tracing: Remove unnecessary NULL assignment
----
Documentation/admin-guide/kernel-parameters.txt | 29 +++
Documentation/trace/events.rst | 12 +
Documentation/trace/histogram.rst | 242 ++++++++++++++++----
include/linux/kernel.h | 2 +-
include/linux/trace.h | 12 +
include/linux/trace_seq.h | 5 +
include/linux/tracepoint.h | 4 +-
include/trace/bpf_probe.h | 45 +---
include/trace/perf.h | 46 +---
include/trace/stages/stage3_trace_output.h | 3 +
include/trace/stages/stage6_event_callback.h | 3 +
include/trace/stages/stage7_class_define.h | 1 +
kernel/trace/Kconfig | 20 +-
kernel/trace/kprobe_event_gen_test.c | 2 +-
kernel/trace/ring_buffer.c | 9 +-
kernel/trace/synth_event_gen_test.c | 2 +-
kernel/trace/trace.c | 164 ++++++++++++--
kernel/trace/trace.h | 6 +
kernel/trace/trace_events.c | 13 +-
kernel/trace/trace_events_filter.c | 93 +++++++-
kernel/trace/trace_events_hist.c | 126 +++++++++--
kernel/trace/trace_events_synth.c | 90 +++++++-
kernel/trace/trace_osnoise.c | 2 +-
kernel/trace/trace_seq.c | 23 ++
kernel/trace/trace_synth.h | 1 +
kernel/tracepoint.c | 4 +-
samples/Kconfig | 7 +
samples/Makefile | 1 +
samples/ftrace/Makefile | 1 +
samples/ftrace/ftrace-direct-modify.c | 2 +-
samples/ftrace/ftrace-direct-multi-modify.c | 2 +-
samples/ftrace/ftrace-direct-multi.c | 2 +-
samples/ftrace/ftrace-direct-too.c | 2 +-
samples/ftrace/ftrace-direct.c | 2 +-
samples/ftrace/ftrace-ops.c | 252 +++++++++++++++++++++
samples/user_events/example.c | 4 +-
scripts/tracing/draw_functrace.py | 6 +-
tools/lib/api/fs/tracing_path.c | 4 +-
.../ftrace/test.d/filter/event-filter-function.tc | 58 +++++
.../inter-event/trigger-synthetic-event-stack.tc | 24 ++
.../inter-event/trigger-synthetic-event-syntax.tc | 6 +
tools/tracing/latency/latency-collector.c | 2 +-
42 files changed, 1113 insertions(+), 221 deletions(-)
create mode 100644 samples/ftrace/ftrace-ops.c
create mode 100644 tools/testing/selftests/ftrace/test.d/filter/event-filter-function.tc
create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-synthetic-event-stack.tc
---------------------------
next reply other threads:[~2023-02-20 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 20:44 Steven Rostedt [this message]
2023-02-23 18:47 ` [GIT PULL] tracing: Updates for 6.3 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-03-19 17:42 Steven Rostedt
2023-03-19 17:53 ` pr-tracker-bot
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=20230220154432.12eefbf6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=arnd@arndb.de \
--cc=bagasdotme@gmail.com \
--cc=baijiaju1990@gmail.com \
--cc=bobo.shaobowang@huawei.com \
--cc=dave@stgolabs.net \
--cc=iecedge@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=quic_linyyuan@quicinc.com \
--cc=suagrfillet@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=trix@redhat.com \
--cc=zanussi@kernel.org \
--cc=zwisler@chromium.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