From: Steven Rostedt <rostedt@goodmis.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
dcook@linux.microsoft.com, alanau@linux.microsoft.com,
brauner@kernel.org, akpm@linux-foundation.org,
linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 00/11] tracing/user_events: Remote write ABI
Date: Mon, 20 Feb 2023 17:01:35 -0500 [thread overview]
Message-ID: <20230220170135.3c9bea01@rorschach.local.home> (raw)
In-Reply-To: <20230120230518.17697-1-beaub@linux.microsoft.com>
On Fri, 20 Jan 2023 15:05:07 -0800
Beau Belgrave <beaub@linux.microsoft.com> wrote:
> Documentation/trace/user_events.rst | 177 ++--
> fs/exec.c | 2 +
> include/linux/sched.h | 5 +
> include/linux/user_events.h | 101 +-
> include/uapi/linux/user_events.h | 81 ++
> kernel/exit.c | 2 +
> kernel/fork.c | 2 +
There's several files that are touched outside of the tracing
subsystem. You may need to run get_maintainers on this to get their
input. I started playing a little with this, but it won't mean anything
if we get push back from these maintainers.
-- Steve
> kernel/trace/Kconfig | 5 +-
> kernel/trace/trace_events_user.c | 863 +++++++++++++++---
> samples/user_events/example.c | 47 +-
> tools/testing/selftests/user_events/Makefile | 2 +-
> .../testing/selftests/user_events/abi_test.c | 226 +++++
> .../testing/selftests/user_events/dyn_test.c | 2 +-
> .../selftests/user_events/ftrace_test.c | 162 ++--
> .../testing/selftests/user_events/perf_test.c | 39 +-
> 15 files changed, 1317 insertions(+), 399 deletions(-)
> create mode 100644 include/uapi/linux/user_events.h
> create mode 100644 tools/testing/selftests/user_events/abi_test.c
>
>
> base-commit: 5dc4c995db9eb45f6373a956eb1f69460e69e6d4
next prev parent reply other threads:[~2023-02-20 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 23:05 [PATCH v7 00/11] tracing/user_events: Remote write ABI Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 01/11] tracing/user_events: Split header into uapi and kernel Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 02/11] tracing/user_events: Track fork/exec/exit for mm lifetime Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 03/11] tracing/user_events: Use remote writes for event enablement Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 04/11] tracing/user_events: Fixup enable faults asyncly Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 05/11] tracing/user_events: Add ioctl for disabling addresses Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 06/11] tracing/user_events: Update self-tests to write ABI Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 07/11] tracing/user_events: Add ABI self-test Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 08/11] tracing/user_events: Use write ABI in example Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 09/11] tracing/user_events: Update documentation for ABI Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 10/11] tracing/user_events: Charge event allocs to cgroups Beau Belgrave
2023-01-20 23:05 ` [PATCH v7 11/11] tracing/user_events: Limit global user_event count Beau Belgrave
2023-02-20 22:01 ` Steven Rostedt [this message]
2023-02-21 17:42 ` [PATCH v7 00/11] tracing/user_events: Remote write ABI Beau Belgrave
2023-02-21 19:35 ` 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=20230220170135.3c9bea01@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=alanau@linux.microsoft.com \
--cc=beaub@linux.microsoft.com \
--cc=brauner@kernel.org \
--cc=dcook@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).