From: Peter Zijlstra <peterz@infradead.org>
To: Alexei Starovoitov <ast@fb.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Brendan Gregg <bgregg@netflix.com>,
Daniel Borkmann <daniel@iogearbox.net>, Teng Qin <qinteng@fb.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 1/3] perf, bpf: Add BPF support to all perf_event types
Date: Mon, 29 May 2017 11:12:53 +0200 [thread overview]
Message-ID: <20170529091253.lopsd33qticsbgii@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20170526055549.557818-2-ast@fb.com>
On Thu, May 25, 2017 at 10:55:47PM -0700, Alexei Starovoitov wrote:
> +++ b/kernel/bpf/arraymap.c
> @@ -462,26 +462,22 @@ static void *perf_event_fd_array_get_ptr(struct bpf_map *map,
>
> event = perf_file->private_data;
> ee = ERR_PTR(-EINVAL);
> + /* Per-task events are not supported */
> + if (event->attach_state & PERF_ATTACH_TASK)
> + goto err_out;
>
> attr = perf_event_attrs(event);
> if (IS_ERR(attr) || attr->inherit)
> goto err_out;
> + /* TRACEPOINT and BREAKPOINT not supported in perf_event_read_local */
I cannot find reason for this comment. That is, why would
perf_event_read_local() not support those two types?
> + if (attr->type == PERF_TYPE_TRACEPOINT ||
> + attr->type == PERF_TYPE_BREAKPOINT)
> + goto err_out;
>
> + ee = bpf_event_entry_gen(perf_file, map_file);
> + if (ee)
> + return ee;
> + ee = ERR_PTR(-ENOMEM);
>
> err_out:
> fput(perf_file);
next prev parent reply other threads:[~2017-05-29 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 5:55 [PATCH v2 net-next 0/3] bpf: Add BPF support to all perf_event Alexei Starovoitov
2017-05-26 5:55 ` [PATCH v2 net-next 1/3] perf, bpf: Add BPF support to all perf_event types Alexei Starovoitov
2017-05-26 11:04 ` kbuild test robot
2017-05-26 14:55 ` David Miller
2017-05-29 9:12 ` Peter Zijlstra [this message]
2017-05-29 9:39 ` Peter Zijlstra
2017-05-30 15:52 ` Alexei Starovoitov
2017-05-30 16:51 ` Peter Zijlstra
2017-05-30 17:37 ` Alexei Starovoitov
2017-05-30 19:03 ` Peter Zijlstra
2017-06-01 13:32 ` Peter Zijlstra
2017-06-01 15:21 ` Alexei Starovoitov
2017-05-26 5:55 ` [PATCH v2 net-next 2/3] samples/bpf: add samples for more perf event types Alexei Starovoitov
2017-05-26 5:55 ` [PATCH v2 net-next 3/3] bpf: update perf event helper functions documentation Alexei Starovoitov
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=20170529091253.lopsd33qticsbgii@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ast@fb.com \
--cc=bgregg@netflix.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qinteng@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
all inboxes | Powered by JetHome®