From: Wang Nan <wangnan0@huawei.com>
To: <acme@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <ast@plumgrid.com>,
<brendan.d.gregg@gmail.com>, <daniel@iogearbox.net>,
<dsahern@gmail.com>, <hekuang@huawei.com>, <jolsa@kernel.org>,
<xiakaixu@huawei.com>, <masami.hiramatsu.pt@hitachi.com>,
<namhyung@kernel.org>, <a.p.zijlstra@chello.nl>,
<lizefan@huawei.com>, <pi3orama@163.com>,
Wang Nan <wangnan0@huawei.com>
Subject: [PATCH 0/4] perf tools: Allow adding --filter to BPF object
Date: Fri, 28 Aug 2015 06:20:17 +0000 [thread overview]
Message-ID: <1440742821-44548-1-git-send-email-wangnan0@huawei.com> (raw)
This 4 patches will be appended into my next perf BPF pull request.
Without them, current perf BPF implementation has a small problem that,
if passing '--filter' after '--event test_bpf.o' event selection, the
filter won't be correctly applied.
Patch 1/4 append a new function to libbpf which allow fetching
object name from bpf_object.
Patch 2/4 add a safety check to avoid access invalid memory if the list
is empty during event parsing.
Patch 3/4 introduces a dummy evsel mechanism.
Patch 4/4 utilizes dummy evsel mechanism, make BPF event collect filter
options by dummy evsel and sync with them after real evsel generated.
The 4th patch should be applied after patch 'perf tools: Add bpf_fd
field to evsel and config it'. Patch 'perf tools: Enable passing bpf
object file to --event' should also be modified to utilize dummy evsel.
Please see my following pull request.
Thank you.
--
1.8.3.4
next reply other threads:[~2015-08-28 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 6:20 Wang Nan [this message]
2015-08-28 6:20 ` [PATCH 01/32] bpf tools: New API to get name from a " Wang Nan
2015-09-01 8:30 ` [tip:perf/urgent] " tip-bot for Wang Nan
2015-08-28 6:20 ` [PATCH 02/32] perf tools: Don't set cmdline_group_boundary if no evsel is collected Wang Nan
2015-08-28 6:20 ` [PATCH 03/32] perf tools: Introduce dummy evsel Wang Nan
2015-08-28 6:20 ` [PATCH 12/32] perf tools: Allow filter option to be applied to bof object Wang Nan
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=1440742821-44548-1-git-send-email-wangnan0@huawei.com \
--to=wangnan0@huawei.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=ast@plumgrid.com \
--cc=brendan.d.gregg@gmail.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=masami.hiramatsu.pt@hitachi.com \
--cc=namhyung@kernel.org \
--cc=pi3orama@163.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
all inboxes | Powered by JetHome®