From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Wang Nan <wangnan0@huawei.com>
Cc: pi3orama@163.com, linux-kernel@vger.kernel.org,
lizefan@huawei.com, Wang Nan <wangnan0@hauwei.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH 3/4] perf bpf: Clone bpf stdout events in multiple bpf scripts
Date: Fri, 8 Apr 2016 14:35:20 -0300 [thread overview]
Message-ID: <20160408173520.GR5945@kernel.org> (raw)
In-Reply-To: <1460128045-97310-4-git-send-email-wangnan0@huawei.com>
Em Fri, Apr 08, 2016 at 03:07:24PM +0000, Wang Nan escreveu:
> This patch allows cloning bpf-output event configuration among multiple
> bpf scripts. If there exist a map named '__bpf_output__' and not configured
> using 'map:__bpf_output__.event=', this patch clones the configuration of
> another '__bpf_stdout__' map. For example, following command:
>
> # perf trace --ev bpf-output/no-inherit,name=evt/ \
> --ev ./test_bpf_trace.c/map:__bpf_stdout__.event=evt/ \
> --ev ./test_bpf_trace2.c usleep 100000
>
> equals to:
>
> # perf trace --ev bpf-output/no-inherit,name=evt/ \
> --ev ./test_bpf_trace.c/map:__bpf_stdout__.event=evt/ \
> --ev ./test_bpf_trace2.c/map:__bpf_stdout__.event=evt/ \
> usleep 100000
I'm fixing it, minor stuff, thanks for working on this!
[acme@jouet linux]$ am /wb/1.patch
Applying: perf bpf: Clone bpf stdout events in multiple bpf scripts
/home/acme/git/linux/.git/rebase-apply/patch:135: trailing whitespace.
/home/acme/git/linux/.git/rebase-apply/patch:140: trailing whitespace.
/*
/home/acme/git/linux/.git/rebase-apply/patch:158: trailing whitespace.
error: patch failed: tools/perf/builtin-trace.c:3289
error: tools/perf/builtin-trace.c: patch does not apply
next prev parent reply other threads:[~2016-04-08 17:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 15:07 [PATCH 0/4] perf bpf: Add __bpf_stdout__ support Wang Nan
2016-04-08 15:07 ` [PATCH 1/4] perf trace: Improve error message when receive non-tracepoint events Wang Nan
2016-04-08 15:22 ` Arnaldo Carvalho de Melo
2016-04-08 16:12 ` Wangnan (F)
2016-04-08 17:33 ` Arnaldo Carvalho de Melo
2016-04-08 15:07 ` [PATCH 2/4] perf trace: Print content of bpf-output event Wang Nan
2016-04-08 15:55 ` Wangnan (F)
2016-04-08 17:25 ` Arnaldo Carvalho de Melo
2016-04-08 15:07 ` [PATCH 3/4] perf bpf: Clone bpf stdout events in multiple bpf scripts Wang Nan
2016-04-08 17:35 ` Arnaldo Carvalho de Melo [this message]
2016-04-13 7:22 ` [tip:perf/core] " tip-bot for Wang Nan
2016-04-08 15:07 ` [PATCH 4/4] perf bpf: Automatically create bpf-output event __bpf_stdout__ Wang Nan
2016-04-08 17:54 ` Arnaldo Carvalho de Melo
2016-04-13 7:22 ` [tip:perf/core] " tip-bot for 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=20160408173520.GR5945@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=pi3orama@163.com \
--cc=wangnan0@hauwei.com \
--cc=wangnan0@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).