From: David Ahern <dsahern@gmail.com>
To: Song Liu <songliubraving@fb.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Netdev <netdev@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>,
"ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"acme@kernel.org" <acme@kernel.org>
Subject: Re: [RFC perf,bpf 1/5] perf, bpf: Introduce PERF_RECORD_BPF_EVENT
Date: Fri, 9 Nov 2018 10:08:07 -0700 [thread overview]
Message-ID: <37d2c7a8-fe99-94bd-9b8f-24e9ca9fa39c@gmail.com> (raw)
In-Reply-To: <050ABAC6-6C3B-4B6B-BB68-727127E00B51@fb.com>
On 11/8/18 11:49 AM, Song Liu wrote:
> Could you please point me to more information about the use cases you worry
> about? I am more than happy to optimize the logic for those use cases.
bpf load and unload as just another tracepoint to throw into a set of
events that are monitored. As mentioned before auditing the loads and
unloads is one example.
And that brings up another comment: Why are you adding a PERF_RECORD_*
rather than a tracepoint? From what I can see the PERF_RECORD_BPF_EVENT
definition does not include the who is loading / unloading a bpf
program. That is important information as well.
next prev parent reply other threads:[~2018-11-09 17:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 20:52 [RFC perf,bpf 0/5] reveal invisible bpf programs Song Liu
2018-11-06 20:52 ` [RFC perf,bpf 1/5] perf, bpf: Introduce PERF_RECORD_BPF_EVENT Song Liu
2018-11-07 8:40 ` Peter Zijlstra
2018-11-07 18:25 ` Song Liu
2018-11-08 15:00 ` Peter Zijlstra
2018-11-08 18:04 ` Song Liu
2018-11-08 18:26 ` David Ahern
2018-11-08 18:49 ` Song Liu
2018-11-09 17:08 ` David Ahern [this message]
2018-11-09 18:49 ` Song Liu
2018-11-09 19:14 ` Alexei Starovoitov
2018-11-06 20:52 ` [RFC perf,bpf 2/5] perf: sync tools/include/uapi/linux/perf_event.h Song Liu
2018-11-06 20:52 ` [RFC perf,bpf 3/5] perf util: basic handling of PERF_RECORD_BPF_EVENT Song Liu
2018-11-06 20:52 ` [RFC perf,bpf 4/5] perf util: introduce bpf_prog_info_event Song Liu
2018-11-06 21:11 ` Alexei Starovoitov
2018-11-06 20:52 ` [RFC perf,bpf 5/5] perf util: generate bpf_prog_info_event for short living bpf programs Song Liu
2018-11-06 21:54 ` David Ahern
2018-11-06 23:17 ` Song Liu
2018-11-06 23:29 ` Alexei Starovoitov
2018-11-06 23:36 ` David Miller
2018-11-07 0:13 ` Alexei Starovoitov
2018-11-07 0:23 ` David Ahern
2018-11-07 0:26 ` Alexei Starovoitov
2018-11-07 0:44 ` David Ahern
2018-11-07 1:09 ` Alexei Starovoitov
2018-11-07 18:12 ` David Ahern
2018-11-07 18:28 ` Song Liu
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=37d2c7a8-fe99-94bd-9b8f-24e9ca9fa39c@gmail.com \
--to=dsahern@gmail.com \
--cc=Kernel-team@fb.com \
--cc=acme@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.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).