mirror of https://lore.kernel.org/lkml/
 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 00/13] tracing/ring-buffer: Persistent traces across a reboot or crash
Date: Fri, 14 Jun 2024 12:30:15 -0400	[thread overview]
Message-ID: <20240614163015.456541709@goodmis.org> (raw)


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

Head SHA1: a62b4f6fbdffa8e90959da485b68f844241d300f


Steven Rostedt (Google) (13):
      ring-buffer: Allow mapped field to be set without mapping
      ring-buffer: Add ring_buffer_alloc_range()
      ring-buffer: Add ring_buffer_meta data
      tracing: Implement creating an instance based on a given memory region
      ring-buffer: Add output of ring buffer meta page
      ring-buffer: Add test if range of boot buffer is valid
      ring-buffer: Validate boot range memory events
      tracing: Add option to use memmapped memory for trace boot instance
      ring-buffer: Save text and data locations in mapped meta data
      tracing/ring-buffer: Add last_boot_info file to boot instance
      tracing: Handle old buffer mappings for event strings and functions
      tracing: Update function tracing output for previous boot buffer
      tracing: Add last boot delta offset for stack traces

----
 Documentation/admin-guide/kernel-parameters.txt |   9 +
 include/linux/ring_buffer.h                     |  20 +
 kernel/trace/ring_buffer.c                      | 878 +++++++++++++++++++++---
 kernel/trace/trace.c                            | 242 ++++++-
 kernel/trace/trace.h                            |  10 +-
 kernel/trace/trace_output.c                     |  12 +-
 6 files changed, 1056 insertions(+), 115 deletions(-)

             reply	other threads:[~2024-06-14 16:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14 16:30 Steven Rostedt [this message]
2024-06-14 16:30 ` [for-next][PATCH 01/13] ring-buffer: Allow mapped field to be set without mapping Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 02/13] ring-buffer: Add ring_buffer_alloc_range() Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 03/13] ring-buffer: Add ring_buffer_meta data Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 04/13] tracing: Implement creating an instance based on a given memory region Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 05/13] ring-buffer: Add output of ring buffer meta page Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 06/13] ring-buffer: Add test if range of boot buffer is valid Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 07/13] ring-buffer: Validate boot range memory events Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 08/13] tracing: Add option to use memmapped memory for trace boot instance Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 09/13] ring-buffer: Save text and data locations in mapped meta data Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 10/13] tracing/ring-buffer: Add last_boot_info file to boot instance Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 11/13] tracing: Handle old buffer mappings for event strings and functions Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 12/13] tracing: Update function tracing output for previous boot buffer Steven Rostedt
2024-06-14 16:30 ` [for-next][PATCH 13/13] tracing: Add last boot delta offset for stack traces 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=20240614163015.456541709@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

all inboxes | Powered by JetHome®