From: Wang Nan <wangnan0@huawei.com>
To: <acme@kernel.org>, <namhyung@kernel.org>,
<masami.hiramatsu.pt@hitachi.com>, <ast@kernel.org>
Cc: <lizefan@huawei.com>, <pi3orama@163.com>,
<linux-kernel@vger.kernel.org>, Wang Nan <wangnan0@huawei.com>
Subject: [PATCH v3 00/13] perf tools: BPF related update
Date: Mon, 30 Nov 2015 07:32:00 +0000 [thread overview]
Message-ID: <1448868733-225582-1-git-send-email-wangnan0@huawei.com> (raw)
This patch set is based on perf/core.
Compare with v2:
- Checks return value of strdup()
- Change BPF map setting syntax to 'maps:[mapname].[event:value]<indices>=value'
For example:
'maps:mapname.value[1,3...5]=10'
Test cases in each commit message are also changed correspondingly.
(Thanks to Namhyung Kim)
This patch set improves perf's BPF support:
- Support filling BPF array with values
Users are allowed to pass something to BPF program through command
line without changing the program itself.
- Support filling BPF event array with events
BPF program can read PMU counters through BPF's perf_event_read()
helper.
- Support bpf_output_event() helper
BPF program can issue perf event to perf.data.
In most of the patches I list commands for testing them, both normal
case and error case.
He Kuang (2):
perf tools: Support perf event alias name
perf record: Support custom vmlinux path
Wang Nan (11):
tools lib bpf: Check return value of strdup when reading map names
perf tools: Add API to config maps in bpf object
perf tools: Enable BPF object configure syntax
perf record: Apply config to BPF objects before recording
perf tools: Enable passing event to BPF object
perf tools: Support setting different slots in a BPF map separately
perf tools: Enable indices setting syntax for BPF maps
perf tools: Introduce bpf-output event
perf data: Add u32_hex data type
perf data: Support converting data from bpf_perf_event_output()
perf tools: Always give options even it not compiled
tools/lib/bpf/libbpf.c | 13 +-
tools/perf/Documentation/perf-record.txt | 10 +-
tools/perf/builtin-probe.c | 15 +-
tools/perf/builtin-record.c | 36 +-
tools/perf/util/bpf-loader.c | 700 +++++++++++++++++++++++++++++++
tools/perf/util/bpf-loader.h | 59 +++
tools/perf/util/data-convert-bt.c | 117 +++++-
tools/perf/util/evlist.c | 16 +
tools/perf/util/evlist.h | 4 +
tools/perf/util/evsel.c | 7 +
tools/perf/util/evsel.h | 1 +
tools/perf/util/parse-events.c | 125 +++++-
tools/perf/util/parse-events.h | 20 +-
tools/perf/util/parse-events.l | 16 +-
tools/perf/util/parse-events.y | 123 +++++-
tools/perf/util/parse-options.c | 113 ++++-
tools/perf/util/parse-options.h | 5 +
17 files changed, 1345 insertions(+), 35 deletions(-)
--
1.8.3.4
next reply other threads:[~2015-11-30 7:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 7:32 Wang Nan [this message]
2015-11-30 7:32 ` [PATCH v3 01/13] tools lib bpf: Check return value of strdup when reading map names Wang Nan
2015-11-30 8:40 ` Namhyung Kim
2015-11-30 7:32 ` [PATCH v3 02/13] perf tools: Add API to config maps in bpf object Wang Nan
2015-11-30 7:32 ` [PATCH v3 03/13] perf tools: Enable BPF object configure syntax Wang Nan
2015-11-30 7:32 ` [PATCH v3 04/13] perf record: Apply config to BPF objects before recording Wang Nan
2015-11-30 7:32 ` [PATCH v3 05/13] perf tools: Support perf event alias name Wang Nan
2015-11-30 7:32 ` [PATCH v3 06/13] perf tools: Enable passing event to BPF object Wang Nan
2015-11-30 7:32 ` [PATCH v3 07/13] perf tools: Support setting different slots in a BPF map separately Wang Nan
2015-11-30 7:32 ` [PATCH v3 08/13] perf tools: Enable indices setting syntax for BPF maps Wang Nan
2015-11-30 7:32 ` [PATCH v3 09/13] perf tools: Introduce bpf-output event Wang Nan
2015-11-30 7:32 ` [PATCH v3 10/13] perf data: Add u32_hex data type Wang Nan
2015-11-30 7:32 ` [PATCH v3 11/13] perf data: Support converting data from bpf_perf_event_output() Wang Nan
2015-11-30 7:32 ` [PATCH v3 12/13] perf tools: Always give options even it not compiled Wang Nan
2015-11-30 7:32 ` [PATCH v3 13/13] perf record: Support custom vmlinux path 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=1448868733-225582-1-git-send-email-wangnan0@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@kernel.org \
--cc=ast@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 \
/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