From: Steven Rostedt <rostedt@goodmis.org>
To: Beau Belgrave <beaub@linux.microsoft.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-trace-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
David Vernet <void@manifault.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
dthaler@microsoft.com, brauner@kernel.org, hch@infradead.org
Subject: Re: [PATCH] tracing/user_events: Run BPF program if attached
Date: Mon, 15 May 2023 17:57:12 -0400 [thread overview]
Message-ID: <20230515175712.649aa5f6@gandalf.local.home> (raw)
In-Reply-To: <20230515192407.GA85@W11-BEAU-MD.localdomain>
On Mon, 15 May 2023 12:24:07 -0700
Beau Belgrave <beaub@linux.microsoft.com> wrote:
> > Beau,
> > please provide a detailed explanation of your use case and how bpf helps.
> >
>
> There are teams that have existing BPF programs that want to also pull
> in data from user processes in addition to the data they already collect
> from the kernel.
>
> We are also seeing a trend of teams wanting to drop buffering approaches
> and move into non-buffered analysis of problems. An example is as soon
> as a fault happens in a user-process, they would like the ability to see
> what that thread has done, what the kernel did a bit before the error
> (or other processes that have swapped in, etc).
>
> We also have needs to aggregate operation duration live, and as soon as
> they deviate, trigger corrective actions. BPF is ideal for us to use for
> aggregating data cheaply, comparing that to other kernel and user
> processes, and then making a decision quickly on how to mitigate or flag
> it. We are working with OpenTelemetry teams to make this work via
> certain exporters in various languages (C#/C++/Rust).
This is turning into a very productive discussion. Thank you Alexei and
Beau for this.
Beau,
Could you possibly also add (in a separate patch), a simple use case of a
BPF program that would be attached to some user event. Could be contrived.
Perhaps supply a patch to ls.c[1] that adds a user event to where it reads a
file type and the bpf program can do something special if the file belongs
to the user. OK, I'm just pulling crazy ideas out of thin air!
[1] https://github.com/coreutils/coreutils/blob/master/src/ls.c
Could copy the ls with the user event to the samples directory for user
events. It is GPL.
-- Steve
next prev parent reply other threads:[~2023-05-15 21:57 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:37 [PATCH] tracing/user_events: Run BPF program if attached Beau Belgrave
2023-05-09 15:24 ` Alexei Starovoitov
2023-05-09 17:01 ` Steven Rostedt
2023-05-09 20:30 ` Steven Rostedt
2023-05-09 20:42 ` Steven Rostedt
2023-05-15 16:57 ` Alexei Starovoitov
2023-05-15 18:33 ` Steven Rostedt
2023-05-15 19:35 ` Beau Belgrave
2023-05-15 21:38 ` Steven Rostedt
2023-05-15 19:24 ` Beau Belgrave
2023-05-15 21:57 ` Steven Rostedt [this message]
2023-05-17 0:36 ` Alexei Starovoitov
2023-05-17 0:56 ` Linus Torvalds
2023-05-17 1:46 ` Linus Torvalds
2023-05-17 2:29 ` Steven Rostedt
2023-05-17 3:03 ` Linus Torvalds
2023-05-17 17:22 ` Beau Belgrave
2023-05-17 18:15 ` Linus Torvalds
2023-05-17 19:07 ` Beau Belgrave
2023-05-17 19:26 ` Linus Torvalds
2023-05-17 19:36 ` Beau Belgrave
2023-05-17 19:36 ` Linus Torvalds
2023-05-17 19:37 ` Linus Torvalds
2023-05-17 23:00 ` Beau Belgrave
2023-05-17 23:14 ` Linus Torvalds
2023-05-17 23:25 ` Steven Rostedt
2023-05-18 0:14 ` Beau Belgrave
2023-05-18 0:23 ` Linus Torvalds
2023-05-17 20:08 ` Linus Torvalds
2023-05-17 1:26 ` Steven Rostedt
2023-05-17 16:50 ` Beau Belgrave
2023-05-18 0:10 ` Alexei Starovoitov
2023-05-18 0:19 ` Beau Belgrave
2023-05-18 0:56 ` Alexei Starovoitov
2023-05-18 1:18 ` Beau Belgrave
2023-05-18 2:08 ` Steven Rostedt
2023-05-18 3:14 ` Alexei Starovoitov
2023-05-18 13:36 ` Steven Rostedt
2023-05-18 17:28 ` Beau Belgrave
2023-06-01 9:46 ` Christian Brauner
2023-06-01 15:24 ` Beau Belgrave
2023-06-01 15:57 ` Christian Brauner
2023-06-01 16:29 ` Beau Belgrave
2023-06-06 13:37 ` Masami Hiramatsu
2023-06-06 17:05 ` Beau Belgrave
2023-06-07 14:07 ` Masami Hiramatsu
2023-06-07 19:26 ` Beau Belgrave
2023-06-08 0:25 ` Masami Hiramatsu
2023-05-17 17:51 ` Beau Belgrave
2023-06-06 13:57 ` Masami Hiramatsu
2023-06-06 16:57 ` Andrii Nakryiko
2023-06-06 20:57 ` Beau Belgrave
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=20230515175712.649aa5f6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dthaler@microsoft.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=void@manifault.com \
/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).