From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: "Wangnan (F)" <wangnan0@huawei.com>,
acme@kernel.org, ast@plumgrid.com, brendan.d.gregg@gmail.com,
daniel@iogearbox.net, namhyung@kernel.org, paulus@samba.org,
a.p.zijlstra@chello.nl, mingo@redhat.com, jolsa@kernel.org,
dsahern@gmail.com
Cc: linux-kernel@vger.kernel.org, lizefan@huawei.com,
hekuang@huawei.com, xiakaixu@huawei.com, pi3orama@163.com,
cti.systems-productivity-manager.ts@hitachi.com
Subject: Re: [RFC PATCH 1/3] perf probe: Init symbol as kprobe if any pev is kprobe
Date: Sat, 27 Jun 2015 17:30:58 +0900 [thread overview]
Message-ID: <558E5F42.1060705@hitachi.com> (raw)
In-Reply-To: <558E520E.6070301@huawei.com>
Hi Wang,
On 2015/06/27 16:34, Wangnan (F) wrote:
>
>
> On 2015/6/27 15:29, Masami Hiramatsu wrote:
>> On 2015/06/25 19:37, Wang Nan wrote:
>>> Before this patch, add_perf_probe_events() init symbol maps only for
>>> uprobe if the first pev passed to it is a uprobe event. However, with
>>> the incoming BPF uprobe support, now it will be possible to pass an
>>> array with combined kprobe and uprobe events to add_perf_probe_events().
>> This description is not correct. Actually, add_perf_probe_events already
>> supports mix of uprobes and kprobes. However, from the command line syntax
>> constrains the first elements of the probe_event arrays must be kprobes.
>> So, if the array starts with uprobes, no kprobes should be there.
>>
>>> This patch check all pevs instead of the first one, and init kernel
>>> symbol if any events is not uprobe.
>> Anyway, I prefer to call init_symbol_maps() with "false" :)
>
> I also prefer "false", so I try to find whether all events are uprobe
> instead
> of init_symbol_maps(true).
>
> So for this patch only commit message needs to be corrected, the code is
> no problem, right?
>
No, I meant you just need to change one line, as below.
- ret = init_symbol_maps(pevs->uprobes);
+ ret = init_symbol_maps(false);
That's enough, I don't like to introduce a bool flag and loop.
Thanks,
> Thank you.
>
>> Thank you,
>>
>>> Signed-off-by: Wang Nan <wangnan0@huawei.com>
>>> ---
>>> tools/perf/util/probe-event.c | 15 ++++++++++++++-
>>> 1 file changed, 14 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
>>> index b386d2f..a2b3026 100644
>>> --- a/tools/perf/util/probe-event.c
>>> +++ b/tools/perf/util/probe-event.c
>>> @@ -2802,8 +2802,21 @@ int cleanup_perf_probe_event(struct perf_probe_event *pev)
>>> int add_perf_probe_events(struct perf_probe_event *pevs, int npevs, bool cleanup)
>>> {
>>> int i, ret;
>>> + bool user_only = true;
>>>
>>> - ret = init_symbol_maps(pevs->uprobes);
>>> + /* If any pev is kprobe, init kernel symbols. */
>>> + for (i = 0; i < npevs; i++) {
>>> + if (!pevs[i].uprobes) {
>>> + user_only = false;
>>> + break;
>>> + }
>>> + }
>>> +
>>> + /*
>>> + * Compiler can drop user_only:
>>> + * ret = init_symbol_maps(i >= npevs);
>>> + */
>>> + ret = init_symbol_maps(user_only);
>>> if (ret < 0)
>>> return ret;
>>>
>>>
>>
>
>
>
--
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2015-06-27 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 10:37 [RFC PATCH 0/3] tracing, perf tools: Attach BPF program on uprobe events Wang Nan
2015-06-25 10:37 ` [RFC PATCH 1/3] perf probe: Init symbol as kprobe if any pev is kprobe Wang Nan
2015-06-26 8:49 ` Alexei Starovoitov
2015-06-27 7:29 ` Masami Hiramatsu
2015-06-27 7:34 ` Wangnan (F)
2015-06-27 8:30 ` Masami Hiramatsu [this message]
2015-06-27 11:15 ` Wangnan (F)
2015-06-25 10:37 ` [RFC PATCH 2/3] tracing, perf: Implement BPF programs attached to uprobes Wang Nan
2015-06-26 8:45 ` Alexei Starovoitov
2015-06-25 10:37 ` [RFC PATCH 3/3] perf tools: Support attach BPF program on uprobe events Wang Nan
2015-06-26 8:47 ` Alexei Starovoitov
2015-06-26 11:09 ` Wangnan (F)
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=558E5F42.1060705@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ast@plumgrid.com \
--cc=brendan.d.gregg@gmail.com \
--cc=cti.systems-productivity-manager.ts@hitachi.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.com \
--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).