From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 00/11] tracing: Updates for 6.3
Date: Tue, 07 Feb 2023 20:56:33 -0500 [thread overview]
Message-ID: <20230208015633.791198913@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next
Head SHA1: 9c1c251d670bc107b9ce600a2c20adb08b4849e9
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
Linyu Yuan (1):
tracing: Acquire buffer from temparary trace sequence
Song Shuai (1):
samples: ftrace: Include the nospec-branch.h only for x86
Steven Rostedt (Google) (5):
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
Tom Rix (1):
samples: ftrace: Make some global variables static
----
Documentation/admin-guide/kernel-parameters.txt | 29 +++++
Documentation/trace/histogram.rst | 93 +++++++-------
include/linux/trace.h | 12 ++
include/linux/trace_seq.h | 5 +
include/trace/stages/stage3_trace_output.h | 3 +
include/trace/stages/stage7_class_define.h | 1 +
kernel/trace/trace.c | 160 +++++++++++++++++++++---
kernel/trace/trace.h | 2 +
kernel/trace/trace_events.c | 9 +-
kernel/trace/trace_events_synth.c | 4 +-
kernel/trace/trace_osnoise.c | 2 +-
kernel/trace/trace_seq.c | 23 ++++
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 | 26 ++--
18 files changed, 290 insertions(+), 89 deletions(-)
next reply other threads:[~2023-02-08 1:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 1:56 Steven Rostedt [this message]
2023-02-08 1:56 ` [for-next][PATCH 01/11] tracing/osnoise: No need for schedule_hrtimeout range Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 02/11] tracing/histogram: Wrap remaining shell snippets in code blocks Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 03/11] tracing: Acquire buffer from temparary trace sequence Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 04/11] samples: ftrace: Include the nospec-branch.h only for x86 Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 05/11] ftrace: sample: avoid open-coded 64-bit division Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 06/11] samples: ftrace: Make some global variables static Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 07/11] tracing: Fix trace_event_raw_event_synth() if else statement Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 08/11] tracing: Add creation of instances at boot command line Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 09/11] tracing: Add enabling of events to boot instances Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 10/11] tracing: Add trace_array_puts() to write into instance Steven Rostedt
2023-02-08 1:56 ` [for-next][PATCH 11/11] tracing: Allow boot instances to have snapshot buffers 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=20230208015633.791198913@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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®