From: Song Liu <songliubraving@fb.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"acme@kernel.org" <acme@kernel.org>,
"ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
Kernel Team <Kernel-team@fb.com>,
"dsahern@gmail.com" <dsahern@gmail.com>
Subject: Re: [PATCH v10 perf, bpf-next 3/9] perf, bpf: introduce PERF_RECORD_BPF_EVENT
Date: Thu, 17 Jan 2019 13:49:19 +0000 [thread overview]
Message-ID: <AF388120-70CD-4590-803B-F8F303334726@fb.com> (raw)
In-Reply-To: <20190117130952.GG10486@hirez.programming.kicks-ass.net>
Thanks Peter!
> On Jan 17, 2019, at 5:09 AM, Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Wed, Jan 16, 2019 at 08:29:25AM -0800, Song Liu wrote:
>> + /*
>> + * Record bpf events:
>> + * enum perf_bpf_event_type {
>> + * PERF_BPF_EVENT_UNKNOWN = 0,
>> + * PERF_BPF_EVENT_PROG_LOAD = 1,
>> + * PERF_BPF_EVENT_PROG_UNLOAD = 2,
>> + * };
>> + *
>> + * struct {
>> + * struct perf_event_header header;
>> + * u16 type;
>> + * u16 flags;
>> + * u32 id;
>> + * u8 tag[BPF_TAG_SIZE];
>
> This does forever fix BPF_TAG_SIZE; is that intentional? We could easily
> make that a variable length field like with the other event. Or is that
> value already part of the eBPF ABI?
Yes, BPF_TAG_SIZE is already part of eBPF ABI.
Song
>
>> + * struct sample_id sample_id;
>> + * };
>> + */
>> + PERF_RECORD_BPF_EVENT = 18,
>> @@ -7744,6 +7747,121 @@ void perf_event_ksymbol(u16 ksym_type, u64 addr, u32 len, bool unregister,
>> WARN_ONCE(1, "%s: Invalid KSYMBOL type 0x%x\n", __func__, ksym_type);
>> }
>>
>> +struct perf_bpf_event {
>> + struct bpf_prog *prog;
>> + struct {
>> + struct perf_event_header header;
>> + u16 type;
>> + u16 flags;
>> + u32 id;
>> + u8 tag[BPF_TAG_SIZE];
>> + } event_id;
>> +};
>
>> +static void perf_event_bpf_emit_ksymbols(struct bpf_prog *prog,
>> + enum perf_bpf_event_type type)
>> +{
>> + bool unregister = type == PERF_BPF_EVENT_PROG_UNLOAD;
>> + int i;
>> +
>> + if (prog->aux->func_cnt == 0) {
>> + perf_event_ksymbol(PERF_RECORD_KSYMBOL_TYPE_BPF,
>> + (u64)(unsigned long)prog->bpf_func,
>> + prog->jited_len, unregister,
>> + perf_event_bpf_get_name, prog);
>> + } else {
>> + for (i = 0; i < prog->aux->func_cnt; i++) {
>> + struct bpf_prog *subprog = prog->aux->func[i];
>> +
>> + perf_event_ksymbol(
>> + PERF_RECORD_KSYMBOL_TYPE_BPF,
>> + (u64)(unsigned long)subprog->bpf_func,
>> + subprog->jited_len, unregister,
>> + perf_event_bpf_get_name, subprog);
>> + }
>> + }
>> +}
>
> I still think this is a weird place to do this.. :-) See them patches I
> just send.
>
>> +void perf_event_bpf_event(struct bpf_prog *prog,
>> + enum perf_bpf_event_type type,
>> + u16 flags)
>> +{
>> + struct perf_bpf_event bpf_event;
>> +
>> + if (type <= PERF_BPF_EVENT_UNKNOWN ||
>> + type >= PERF_BPF_EVENT_MAX)
>> + return;
>> +
>> + switch (type) {
>> + case PERF_BPF_EVENT_PROG_LOAD:
>> + case PERF_BPF_EVENT_PROG_UNLOAD:
>> + if (atomic_read(&nr_ksymbol_events))
>> + perf_event_bpf_emit_ksymbols(prog, type);
>> + break;
>> + default:
>> + break;
>> + }
>> +
>> + if (!atomic_read(&nr_bpf_events))
>> + return;
>> +
>> + bpf_event = (struct perf_bpf_event){
>> + .prog = prog,
>> + .event_id = {
>> + .header = {
>> + .type = PERF_RECORD_BPF_EVENT,
>> + .size = sizeof(bpf_event.event_id),
>> + },
>> + .type = type,
>> + .flags = flags,
>> + .id = prog->aux->id,
>> + },
>> + };
>
> BUILD_BUG_ON(BPF_TAG_SIZE % sizeof(u64));
>
>> + memcpy(bpf_event.event_id.tag, prog->tag, BPF_TAG_SIZE);
>> + perf_iterate_sb(perf_event_bpf_output, &bpf_event, NULL);
>> +}
>
> Anyway, small nits only:
>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradeaed.org>
next prev parent reply other threads:[~2019-01-17 13:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 16:29 [PATCH v10 perf, bpf-next 0/9] reveal invisible bpf programs Song Liu
2019-01-16 16:29 ` [PATCH v10 perf, bpf-next 1/9] perf, bpf: Introduce PERF_RECORD_KSYMBOL Song Liu
2019-01-17 12:48 ` Peter Zijlstra
2019-01-17 12:56 ` Peter Zijlstra
2019-01-17 14:49 ` Song Liu
2019-01-17 14:58 ` Arnaldo Carvalho de Melo
2019-01-17 15:02 ` Song Liu
2019-01-18 8:38 ` Peter Zijlstra
2019-01-18 8:41 ` Peter Zijlstra
2019-01-16 16:29 ` [PATCH v10 perf, bpf-next 2/9] sync tools/include/uapi/linux/perf_event.h Song Liu
2019-01-16 16:29 ` [PATCH v10 perf, bpf-next 3/9] perf, bpf: introduce PERF_RECORD_BPF_EVENT Song Liu
2019-01-17 13:09 ` Peter Zijlstra
2019-01-17 13:49 ` Song Liu [this message]
2019-01-16 16:29 ` [PATCH v10 perf, bpf-next 4/9] sync tools/include/uapi/linux/perf_event.h Song Liu
2019-01-16 16:29 ` [PATCH v10 perf, bpf-next 5/9] perf util: handle PERF_RECORD_KSYMBOL Song Liu
2019-01-16 16:29 ` [PATCH v10 perf, bpf-next 6/9] perf util: handle PERF_RECORD_BPF_EVENT Song Liu
2019-01-16 16:29 ` [PATCH v10 perf, bpf-next 7/9] perf tools: synthesize PERF_RECORD_* for loaded BPF programs Song Liu
2019-01-16 16:29 ` [PATCH v10 perf, bpf-next 8/9] perf top: Synthesize BPF events for pre-existing " Song Liu
2019-01-16 16:29 ` [PATCH v10 perf, bpf-next 9/9] bpf: add module name [bpf] to ksymbols for bpf programs Song Liu
2019-01-17 13:10 ` Peter Zijlstra
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=AF388120-70CD-4590-803B-F8F303334726@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=acme@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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).