From: "Wangnan (F)" <wangnan0@huawei.com>
To: Alexei Starovoitov <ast@plumgrid.com>,
"David S. Miller" <davem@davemloft.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@kernel.org>, He Kuang <hekuang@huawei.com>,
Kaixu Xia <xiakaixu@huawei.com>,
Daniel Borkmann <daniel@iogearbox.net>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 net-next] bpf: fix bpf_perf_event_read() helper
Date: Thu, 22 Oct 2015 20:30:36 +0800 [thread overview]
Message-ID: <5628D6EC.3040606@huawei.com> (raw)
In-Reply-To: <1445468283-4592-1-git-send-email-ast@kernel.org>
On 2015/10/22 6:58, Alexei Starovoitov wrote:
[SNIP]
> diff --git a/kernel/bpf/arraymap.c b/kernel/bpf/arraymap.c
> index e3cfe46b074f..75529cc94304 100644
> --- a/kernel/bpf/arraymap.c
> +++ b/kernel/bpf/arraymap.c
> @@ -294,10 +294,11 @@ static void *perf_event_fd_array_get_ptr(struct bpf_map *map, int fd)
> if (IS_ERR(attr))
> return (void *)attr;
>
> - if (attr->type != PERF_TYPE_RAW &&
> - !(attr->type == PERF_TYPE_SOFTWARE &&
> - attr->config == PERF_COUNT_SW_BPF_OUTPUT) &&
> - attr->type != PERF_TYPE_HARDWARE) {
> + if ((attr->type != PERF_TYPE_RAW &&
> + !(attr->type == PERF_TYPE_SOFTWARE &&
> + attr->config == PERF_COUNT_SW_BPF_OUTPUT) &&
> + attr->type != PERF_TYPE_HARDWARE) ||
> + attr->inherit) {
> perf_event_release_kernel(event);
> return ERR_PTR(-EINVAL);
> }
I have a question on inherit, not related to this patch:
Is it safe for perf to disable attr->inherit if the event is system wide?
I haven't read relate code completely. In my current knowledge the behavior
of a system wide perf event should be same whether inherit is set or not.
Is that true?
Thank you.
next prev parent reply other threads:[~2015-10-22 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 22:58 [PATCH v2 net-next] bpf: fix bpf_perf_event_read() helper Alexei Starovoitov
2015-10-22 4:49 ` Wangnan (F)
2015-10-22 5:00 ` Alexei Starovoitov
2015-10-22 5:30 ` Wangnan (F)
2015-10-22 5:31 ` Wangnan (F)
2015-10-22 6:21 ` Alexei Starovoitov
2015-10-22 7:39 ` Wangnan (F)
2015-10-22 15:51 ` Alexei Starovoitov
2015-10-22 12:30 ` Wangnan (F) [this message]
2015-10-22 12:41 ` Peter Zijlstra
2015-10-22 13:57 ` Peter Zijlstra
2015-10-22 15:53 ` 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=5628D6EC.3040606@huawei.com \
--to=wangnan0@huawei.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hekuang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiakaixu@huawei.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).