From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/7] tracing: Updates for 6.7
Date: Wed, 04 Oct 2023 21:53:10 -0400 [thread overview]
Message-ID: <20231005015310.859143353@goodmis.org> (raw)
Beau Belgrave (3):
tracing/user_events: Allow events to persist for perfmon_capable users
selftests/user_events: Test persist flag cases
tracing/user_events: Document persist event flags
Steven Rostedt (Google) (2):
eventfs: Remove eventfs_file and just use eventfs_inode
tracing/selftests: Update kprobe args char/string to match new functions
Uros Bizjak (1):
ring_buffer: Use try_cmpxchg instead of cmpxchg in rb_insert_pages
Zheng Yejian (1):
tracing: Expand all ring buffers individually
----
Documentation/trace/user_events.rst | 21 +-
fs/tracefs/event_inode.c | 847 +++++++++++----------
fs/tracefs/inode.c | 2 +-
fs/tracefs/internal.h | 37 +-
include/linux/trace_events.h | 2 +-
include/linux/tracefs.h | 29 +-
include/uapi/linux/user_events.h | 11 +-
kernel/trace/ring_buffer.c | 8 +-
kernel/trace/trace.c | 54 +-
kernel/trace/trace.h | 13 +-
kernel/trace/trace_events.c | 335 +++++---
kernel/trace/trace_events_user.c | 36 +-
.../ftrace/test.d/kprobe/kprobe_args_char.tc | 4 +-
.../ftrace/test.d/kprobe/kprobe_args_string.tc | 4 +-
tools/testing/selftests/user_events/abi_test.c | 55 +-
tools/testing/selftests/user_events/dyn_test.c | 54 +-
16 files changed, 917 insertions(+), 595 deletions(-)
next reply other threads:[~2023-10-05 1:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 1:53 Steven Rostedt [this message]
2023-10-05 1:53 ` [for-next][PATCH 1/7] tracing: Expand all ring buffers individually Steven Rostedt
2023-10-05 1:53 ` [for-next][PATCH 2/7] ring_buffer: Use try_cmpxchg instead of cmpxchg in rb_insert_pages Steven Rostedt
2023-10-05 1:53 ` [for-next][PATCH 3/7] tracing/user_events: Allow events to persist for perfmon_capable users Steven Rostedt
2023-10-05 1:53 ` [for-next][PATCH 4/7] selftests/user_events: Test persist flag cases Steven Rostedt
2023-10-05 1:53 ` [for-next][PATCH 5/7] tracing/user_events: Document persist event flags Steven Rostedt
2023-10-05 1:53 ` [for-next][PATCH 6/7] eventfs: Remove eventfs_file and just use eventfs_inode Steven Rostedt
2023-10-05 15:06 ` kernel test robot
2023-10-05 1:53 ` [for-next][PATCH 7/7] tracing/selftests: Update kprobe args char/string to match new functions 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=20231005015310.859143353@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.