[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6907d1cd-b132-1aa4-c69e-5277d2d26262@fb.com>
Date: Fri, 9 Nov 2018 19:14:39 +0000
From: Alexei Starovoitov <ast@...com>
To: Song Liu <songliubraving@...com>, David Ahern <dsahern@...il.com>
CC: Peter Zijlstra <peterz@...radead.org>,
Netdev <netdev@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
Kernel Team <Kernel-team@...com>,
"ast@...nel.org" <ast@...nel.org>,
"daniel@...earbox.net" <daniel@...earbox.net>,
"acme@...nel.org" <acme@...nel.org>
Subject: Re: [RFC perf,bpf 1/5] perf, bpf: Introduce PERF_RECORD_BPF_EVENT
On 11/9/18 10:49 AM, Song Liu wrote:
>
>
>> On Nov 9, 2018, at 9:08 AM, David Ahern <dsahern@...il.com> wrote:
>>
>> 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.
>
> For the tracepoint approach, we need similar synchronous logic in perf to
> process BPF load/unload events. If we agree this is the right direction,
> I will modify the set with tracepoints.
we had tracepoints in bpf core. We removed it.
I don't think we'll be going back.
Powered by blists - more mailing lists