[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230220170135.3c9bea01@rorschach.local.home>
Date: Mon, 20 Feb 2023 17:01:35 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Beau Belgrave <beaub@...ux.microsoft.com>
Cc: mhiramat@...nel.org, mathieu.desnoyers@...icios.com,
dcook@...ux.microsoft.com, alanau@...ux.microsoft.com,
brauner@...nel.org, akpm@...ux-foundation.org,
linux-trace-devel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 00/11] tracing/user_events: Remote write ABI
On Fri, 20 Jan 2023 15:05:07 -0800
Beau Belgrave <beaub@...ux.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
Powered by blists - more mailing lists