linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Beau Belgrave <beaub@linux.microsoft.com>
To: Steven Rostedt <rostedt@goodmis.org>
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: Tue, 21 Feb 2023 09:42:51 -0800	[thread overview]
Message-ID: <20230221174251.GA1786@kbox> (raw)
In-Reply-To: <20230220170135.3c9bea01@rorschach.local.home>

On Mon, Feb 20, 2023 at 05:01:35PM -0500, Steven Rostedt wrote:
> 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
> 

Would you prefer I start another version and include the key maintainers
from fs/exec.c, kernel/exit.c, and kernel/fork.c?

I've added akpm and brauner in these patches. I've pinged akpm privately
about these, but didn't get any responses.

It seems like Eric Biederman, Kees Cook, and linux-mm would be good
folks to add here from get_maintainers outputs.

Thoughts?

Thanks,
-Beau

> 
> >  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

  reply	other threads:[~2023-02-21 17:43 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 ` [PATCH v7 00/11] tracing/user_events: Remote write ABI Steven Rostedt
2023-02-21 17:42   ` Beau Belgrave [this message]
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=20230221174251.GA1786@kbox \
    --to=beaub@linux.microsoft.com \
    --cc=akpm@linux-foundation.org \
    --cc=alanau@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 \
    --cc=rostedt@goodmis.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).