| From: |
| He Kuang <hekuang@huawei.com> |
| To: |
| <rostedt@goodmis.org>, <ast@plumgrid.com>, <masami.hiramatsu.pt@hitachi.com>, <acme@kernel.org>, <a.p.zijlstra@chello.nl>, <mingo@redhat.com>, <namhyung@kernel.org>, <jolsa@kernel.org> |
| Subject: |
| [RFC PATCH v5 0/3] Make eBPF programs output data to perf |
| Date: |
| Tue, 14 Jul 2015 01:59:28 +0000 |
| Message-ID: |
| <1436839171-31527-1-git-send-email-hekuang@huawei.com> |
| Cc: |
| <wangnan0@huawei.com>, <pi3orama@163.com>, <linux-kernel@vger.kernel.org>, <hekuang@huawei.com> |
| Archive‑link: | |
Article |
Hi,
Previous patch v4 url:
http://thread.gmane.org/gmane.linux.kernel/1993353
This version we output bpf trace events in a hex array, the results
for three u64 integers in previous sample changed to this:
dd 1042 [000] 1296.122951: bpf:bpf_output_data: 7a ca aa c6 2d 01 00
00 95 87 ec ca 2d 01 00 00 1b bd 41 04 00 00 00 00
Users can interpret their own formats and get the result:
last=0x12dc6aaca7a, cur=0x12dcaec8795, del=0x441bd1b
v3-v4:
- Change u64 array in trace event to u8.
- Remove misleading 'perf event' in subject.
Thank you.
He Kuang (3):
tracing/events: Fix wrong sample output by storing array length
instead of size
tools lib traceevent: Add function to get dynamic arrays length
bpf: Introduce function for outputing trace event data
include/trace/events/bpf.h | 30 +++++++++++++
include/trace/trace_events.h | 5 ++-
include/uapi/linux/bpf.h | 7 +++
kernel/trace/bpf_trace.c | 23 ++++++++++
samples/bpf/bpf_helpers.h | 2 +
tools/lib/traceevent/event-parse.c | 52 ++++++++++++++++++++++
tools/lib/traceevent/event-parse.h | 1 +
.../util/scripting-engines/trace-event-python.c | 1 +
8 files changed, 119 insertions(+), 2 deletions(-)
create mode 100644 include/trace/events/bpf.h
--
1.8.5.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
