From: "Wangnan (F)" <wangnan0@huawei.com>
To: He Kuang <hekuang@huawei.com>,
Steven Rostedt <rostedt@goodmis.org>,
Alexei Starovoitov <ast@plumgrid.com>
Cc: <masami.hiramatsu.pt@hitachi.com>, <acme@kernel.org>,
<a.p.zijlstra@chello.nl>, <mingo@redhat.com>,
<namhyung@kernel.org>, <jolsa@kernel.org>, <pi3orama@163.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v5 0/3] Make eBPF programs output data to perf
Date: Fri, 17 Jul 2015 10:39:29 +0800 [thread overview]
Message-ID: <55A86AE1.8090700@huawei.com> (raw)
In-Reply-To: <55A868F3.5090007@huawei.com>
On 2015/7/17 10:31, He Kuang wrote:
>
> On 2015/7/14 21:35, Steven Rostedt wrote:
>> On Mon, 13 Jul 2015 20:10:29 -0700
>> Alexei Starovoitov <ast@plumgrid.com> wrote:
>>
>>> On 7/13/15 6:59 PM, He Kuang wrote:
>>>> 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
>>>
>>> typo in the above. It's not 3 u64 integers, but variable number of u8.
>>>
>>> Whole thing looks good.
>>> I've acked patch 3.
>>> Hopefully Steven can review patches 1 and 2.
>>
>> I'll try to get around to it ;-)
>>
>> -- Steve
>>
>
> Awaiting your reply ;-)
>
> Thank you.
>
Just for your information:
I collected this 3 patches in my own git tree:
https://github.com/WangNan0/linux ebpf
And I'll collect other patches made by our team there.
Thank you.
prev parent reply other threads:[~2015-07-17 2:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 1:59 [RFC PATCH v5 0/3] Make eBPF programs output data to perf He Kuang
2015-07-14 1:59 ` [RFC PATCH v5 1/3] tracing/events: Fix wrong sample output by storing array length instead of size He Kuang
2015-07-14 1:59 ` [RFC PATCH v5 2/3] tools lib traceevent: Add function to get dynamic arrays length He Kuang
2015-07-17 3:36 ` Wangnan (F)
2015-07-17 14:36 ` Steven Rostedt
2015-07-17 14:43 ` pi3orama
2015-07-14 1:59 ` [RFC PATCH v5 3/3] bpf: Introduce function for outputing trace event data He Kuang
2015-07-14 3:08 ` Alexei Starovoitov
2015-07-14 3:10 ` [RFC PATCH v5 0/3] Make eBPF programs output data to perf Alexei Starovoitov
2015-07-14 13:35 ` Steven Rostedt
2015-07-17 2:31 ` He Kuang
2015-07-17 2:38 ` Steven Rostedt
2015-07-17 2:39 ` Wangnan (F) [this message]
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=55A86AE1.8090700@huawei.com \
--to=wangnan0@huawei.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ast@plumgrid.com \
--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=namhyung@kernel.org \
--cc=pi3orama@163.com \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.