The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Wang Nan <wangnan0@huawei.com>
To: <acme@kernel.org>, <jolsa@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, Wang Nan <wangnan0@huawei.com>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>,
	Li Zefan <lizefan@huawei.com>, <pi3orama@163.com>
Subject: [RFC PATCH 0/5] perf tools: Decode bpf output in 'perf trace'
Date: Thu, 25 Feb 2016 08:51:50 +0000	[thread overview]
Message-ID: <1456390315-127562-1-git-send-email-wangnan0@huawei.com> (raw)

Hi Arnaldo,

  You try to record + analysis using 'perf trace' with BPF output
but failed yesterday. You need these 5 patches to make it work.

Thank you.

Wang Nan (5):
  perf trace: Apply config options in '.perfconfig'
  perf trace: Improve error message when receive non-tracepoint events
  perf tools: Only set filter for tracepoints events
  perf trace: Call bpf__apply_obj_config in 'perf trace'
  perf trace: Print content of bpf-output event

 tools/perf/builtin-trace.c | 71 ++++++++++++++++++++++++++++++++++++++++++++--
 tools/perf/util/evlist.c   |  3 ++
 2 files changed, 72 insertions(+), 2 deletions(-)

Signed-off-by: Wang Nan <wangnan0@huawei.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>
Cc: Li Zefan <lizefan@huawei.com>
Cc: pi3orama@163.com

-- 
1.8.3.4

             reply	other threads:[~2016-02-25  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25  8:51 Wang Nan [this message]
2016-02-25  8:51 ` [RFC PATCH 1/5] perf trace: Apply config options in '.perfconfig' Wang Nan
2016-02-25 12:50   ` Arnaldo Carvalho de Melo
2016-02-25  8:51 ` [RFC PATCH 2/5] perf trace: Improve error message when receive non-tracepoint events Wang Nan
2016-02-25  8:51 ` [RFC PATCH 3/5] perf tools: Only set filter for tracepoints events Wang Nan
2016-02-25  8:51 ` [RFC PATCH 4/5] perf trace: Call bpf__apply_obj_config in 'perf trace' Wang Nan
2016-02-25  8:51 ` [RFC PATCH 5/5] perf trace: Print content of bpf-output event 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=1456390315-127562-1-git-send-email-wangnan0@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=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 \
    /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