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: Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/8] ring-buffer: Updates for 6.12
Date: Tue, 27 Aug 2024 05:27:16 -0400	[thread overview]
Message-ID: <20240827092716.515115830@goodmis.org> (raw)

  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
ring-buffer/for-next

Head SHA1: 2fcd5aff92aab479a9a89cfce2dbc9c6a9455b4f


Steven Rostedt (7):
      ring-buffer: Don't reset persistent ring-buffer meta saved addresses
      ring-buffer: Add magic and struct size to boot up meta data
      tracing: Add "traceoff" flag to boot time tracing instances
      tracing: Allow trace_printk() to go to other instance buffers
      tracing: Have trace_printk not use binary prints if boot buffer
      tracing: Add option to set an instance to be the trace_printk destination
      tracing/Documentation: Start a document on how to debug with tracing

Vincent Donnefort (1):
      ring-buffer: Align meta-page to sub-buffers for improved TLB usage

----
 Documentation/admin-guide/kernel-parameters.txt |  23 ++++
 Documentation/trace/debugging.rst               | 159 ++++++++++++++++++++++++
 Documentation/trace/ftrace.rst                  |  12 ++
 kernel/trace/ring_buffer.c                      |  79 ++++++++----
 kernel/trace/trace.c                            | 127 ++++++++++++++++---
 kernel/trace/trace.h                            |   4 +-
 kernel/trace/trace_output.c                     |   5 +-
 tools/testing/selftests/ring-buffer/map_test.c  |  14 +++
 8 files changed, 385 insertions(+), 38 deletions(-)
 create mode 100644 Documentation/trace/debugging.rst

             reply	other threads:[~2024-08-27  9:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  9:27 Steven Rostedt [this message]
2024-08-27  9:27 ` [for-next][PATCH 1/8] ring-buffer: Dont reset persistent ring-buffer meta saved addresses Steven Rostedt
2024-08-27  9:27 ` [for-next][PATCH 2/8] ring-buffer: Add magic and struct size to boot up meta data Steven Rostedt
2024-08-27  9:27 ` [for-next][PATCH 3/8] ring-buffer: Align meta-page to sub-buffers for improved TLB usage Steven Rostedt
2024-08-27  9:27 ` [for-next][PATCH 4/8] tracing: Add "traceoff" flag to boot time tracing instances Steven Rostedt
2024-08-27  9:27 ` [for-next][PATCH 5/8] tracing: Allow trace_printk() to go to other instance buffers Steven Rostedt
2024-08-27  9:27 ` [for-next][PATCH 6/8] tracing: Have trace_printk not use binary prints if boot buffer Steven Rostedt
2024-08-27  9:27 ` [for-next][PATCH 7/8] tracing: Add option to set an instance to be the trace_printk destination Steven Rostedt
2024-08-27  9:27 ` [for-next][PATCH 8/8] tracing/Documentation: Start a document on how to debug with 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=20240827092716.515115830@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --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