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/6] ring-buffer: Memmory mapping the ring buffer to user space
Date: Tue, 14 May 2024 12:15:58 -0400 [thread overview]
Message-ID: <20240514161558.664348429@goodmis.org> (raw)
ring-buffer/for-next
Head SHA1: fe832be05a8eee5f1488cbcc2c562dd82d079fd6
Steven Rostedt (Google) (1):
ring-buffer: Have mmapped ring buffer keep track of missed events
Vincent Donnefort (5):
ring-buffer: Allocate sub-buffers with __GFP_COMP
ring-buffer: Introducing ring-buffer mapping functions
tracing: Allow user-space mapping of the ring-buffer
Documentation: tracing: Add ring-buffer mapping
ring-buffer/selftest: Add ring-buffer mapping test
----
Documentation/trace/index.rst | 1 +
Documentation/trace/ring-buffer-map.rst | 106 ++++++
include/linux/ring_buffer.h | 6 +
include/uapi/linux/trace_mmap.h | 48 +++
kernel/trace/ring_buffer.c | 471 ++++++++++++++++++++++++-
kernel/trace/trace.c | 104 +++++-
kernel/trace/trace.h | 1 +
tools/testing/selftests/ring-buffer/.gitignore | 1 +
tools/testing/selftests/ring-buffer/Makefile | 8 +
tools/testing/selftests/ring-buffer/config | 2 +
tools/testing/selftests/ring-buffer/map_test.c | 294 +++++++++++++++
11 files changed, 1026 insertions(+), 16 deletions(-)
create mode 100644 Documentation/trace/ring-buffer-map.rst
create mode 100644 include/uapi/linux/trace_mmap.h
create mode 100644 tools/testing/selftests/ring-buffer/.gitignore
create mode 100644 tools/testing/selftests/ring-buffer/Makefile
create mode 100644 tools/testing/selftests/ring-buffer/config
create mode 100644 tools/testing/selftests/ring-buffer/map_test.c
next reply other threads:[~2024-05-14 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 16:15 Steven Rostedt [this message]
2024-05-14 16:15 ` [for-next][PATCH 1/6] ring-buffer: Allocate sub-buffers with __GFP_COMP Steven Rostedt
2024-05-14 16:16 ` [for-next][PATCH 2/6] ring-buffer: Introducing ring-buffer mapping functions Steven Rostedt
2024-05-14 16:16 ` [for-next][PATCH 3/6] tracing: Allow user-space mapping of the ring-buffer Steven Rostedt
2024-05-14 16:16 ` [for-next][PATCH 4/6] Documentation: tracing: Add ring-buffer mapping Steven Rostedt
2024-05-14 16:16 ` [for-next][PATCH 5/6] ring-buffer/selftest: Add ring-buffer mapping test Steven Rostedt
2024-05-14 16:16 ` [for-next][PATCH 6/6] ring-buffer: Have mmapped ring buffer keep track of missed events 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=20240514161558.664348429@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