From: xiakaixu <xiakaixu@huawei.com>
To: Alexei Starovoitov <ast@plumgrid.com>
Cc: <davem@davemloft.net>, <acme@kernel.org>, <mingo@redhat.com>,
<a.p.zijlstra@chello.nl>, <masami.hiramatsu.pt@hitachi.com>,
<jolsa@kernel.org>, <wangnan0@huawei.com>,
<linux-kernel@vger.kernel.org>, <pi3orama@163.com>,
<hekuang@huawei.com>
Subject: Re: [PATCH v2 4/5] bpf: Implement function bpf_perf_event_read() that get the selected hardware PMU conuter
Date: Thu, 23 Jul 2015 10:12:53 +0800 [thread overview]
Message-ID: <55B04DA5.6020807@huawei.com> (raw)
In-Reply-To: <55B04003.3000904@plumgrid.com>
于 2015/7/23 9:14, Alexei Starovoitov 写道:
> On 7/22/15 1:09 AM, Kaixu Xia wrote:
>> According to the perf_event_map_fd and key, the function
>> bpf_perf_event_read() can convert the corresponding map
>> value to the pointer to struct perf_event and return the
>> Hardware PMU counter value.
>>
>> The key can't be passed to bpf_perf_event_read() directly
>> because the function argument constraint is lacked.
>
> I don't understand above sentence.
>
>> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
>> index 69a1f6b..e3bb181 100644
>> --- a/include/uapi/linux/bpf.h
>> +++ b/include/uapi/linux/bpf.h
>> @@ -250,6 +250,8 @@ enum bpf_func_id {
>> * Return: 0 on success
>> */
>> BPF_FUNC_get_current_comm,
>> +
>> + BPF_FUNC_perf_event_read, /* u64 bpf_perf_event_read(&map, &key) */
>
> no need for extra empty line.
>
>> +
>> +static u64 bpf_perf_event_read(u64 r1, u64 r2, u64 r3, u64 r4, u64 r5)
>> +{
>> + struct bpf_map *map = (struct bpf_map *) (unsigned long) r1;
>> + void *key = (void *) (unsigned long) r2;
>> + struct perf_event *event;
>> + void *ptr;
>> +
>> + if (map->map_type != BPF_MAP_TYPE_PERF_EVENT_ARRAY)
>> + return -EINVAL;
>
> please check this statically in verifier instead of in run-time.
>
>> +
>> + rcu_read_lock();
>
> unnecessary.
>
>> + ptr = map->ops->map_lookup_elem(map, key);
>> + rcu_read_unlock();
>> + if (!ptr || !(*(unsigned long *)ptr))
>> + return -EBADF;
>
> all these casts can be removed. First cast of 'r1' into
> perf_event_array will be enough.
So you mean like this?
u64 bpf_perf_event_read(u64 r1, u64 index,...)
{
struct bpf_perf_event_array *array = (void *) (long) r1;
struct perf_event *event;
...
event = array->events[index];
...
}
>
>> +const struct bpf_func_proto bpf_perf_event_read_proto = {
>> + .func = bpf_perf_event_read,
>> + .gpl_only = false,
>> + .ret_type = RET_INTEGER,
>> + .arg1_type = ARG_CONST_MAP_PTR,
>> + .arg2_type = ARG_PTR_TO_MAP_KEY,
>
> make it arg2_type = ARG_ANYTHING then you'll just index
> into array the way prog_array does and similar to bpf_tail_call.
ARG_ANYTHING means any (initialized) argument is ok, but we here
really want is map key. So I'm not sure ARG_ANYTHING is suitable.
You know ARG_ANYTHING is not checked enough in verifier.
Thanks.
>
>
> .
>
next prev parent reply other threads:[~2015-07-23 2:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 8:09 [PATCH v2 0/5] bpf: Introduce the new ability of eBPF programs to access hardware PMU counter Kaixu Xia
2015-07-22 8:09 ` [PATCH v2 1/5] bpf: Add new bpf map type to store the pointer to struct perf_event Kaixu Xia
2015-07-23 0:48 ` Alexei Starovoitov
2015-07-23 1:08 ` Wangnan (F)
2015-07-23 1:39 ` Alexei Starovoitov
2015-07-22 8:09 ` [PATCH v2 2/5] bpf: Add function map->ops->map_traverse_elem() to traverse map elems Kaixu Xia
2015-07-23 1:00 ` Alexei Starovoitov
2015-07-22 8:09 ` [PATCH v2 3/5] bpf: Save the pointer to struct perf_event to map Kaixu Xia
2015-07-23 1:08 ` Alexei Starovoitov
2015-07-22 8:09 ` [PATCH v2 4/5] bpf: Implement function bpf_perf_event_read() that get the selected hardware PMU conuter Kaixu Xia
2015-07-23 1:14 ` Alexei Starovoitov
2015-07-23 2:12 ` xiakaixu [this message]
2015-07-23 2:22 ` Alexei Starovoitov
2015-07-23 2:39 ` xiakaixu
2015-07-22 8:09 ` [PATCH v2 5/5] samples/bpf: example of get selected PMU counter value Kaixu Xia
2015-07-23 1:16 ` Alexei Starovoitov
2015-07-23 23:33 ` [PATCH v2 0/5] bpf: Introduce the new ability of eBPF programs to access hardware PMU counter Daniel Borkmann
2015-07-25 2:14 ` xiakaixu
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=55B04DA5.6020807@huawei.com \
--to=xiakaixu@huawei.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=pi3orama@163.com \
--cc=wangnan0@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