From: Wang Nan <wangnan0@huawei.com>
To: <acme@kernel.org>, <namhyung@kernel.org>
Cc: <lizefan@huawei.com>, <pi3orama@163.com>,
<linux-kernel@vger.kernel.org>, Wang Nan <wangnan0@huawei.com>
Subject: [PATCH v2 0/4] perf bpf: Improve error code delivering and output
Date: Wed, 4 Nov 2015 02:25:55 +0000 [thread overview]
Message-ID: <1446603959-233500-1-git-send-email-wangnan0@huawei.com> (raw)
This patchset is based on perf/core
(commit bebd23a2ed31d47e7dd746d3b125068aa2c42d85 in Arnaldo's tree).
Compare with v1 [1], this patchset changes error reporting convention
and the user of it at one same patch, avoid NULL checking in perf.
Wang Nan (4):
perf test: Keep test result clean if '-v' not set
perf tools: Mute libbpf when '-v' not set
bpf tools: Improve libbpf error reporting
perf tools: Improve BPF related error messages output
tools/lib/bpf/libbpf.c | 149 +++++++++++++++++++++++++------------
tools/lib/bpf/libbpf.h | 12 +++
tools/perf/tests/attr.c | 3 +-
tools/perf/tests/code-reading.c | 8 +-
tools/perf/tests/keep-tracking.c | 4 +-
tools/perf/tests/llvm.c | 13 ++--
tools/perf/tests/switch-tracking.c | 4 +-
tools/perf/util/bpf-loader.c | 110 +++++++++++++++++++++++----
tools/perf/util/bpf-loader.h | 18 +++++
tools/perf/util/parse-events.c | 11 +--
10 files changed, 245 insertions(+), 87 deletions(-)
--
1.8.3.4
next reply other threads:[~2015-11-04 2:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 2:25 Wang Nan [this message]
2015-11-04 2:25 ` [PATCH v2 1/4] perf test: Keep test result clean if '-v' not set Wang Nan
2015-11-04 2:25 ` [PATCH v2 2/4] perf tools: Mute libbpf when " Wang Nan
2015-11-04 2:25 ` [PATCH v2 3/4] bpf tools: Improve libbpf error reporting Wang Nan
2015-11-04 22:01 ` Arnaldo Carvalho de Melo
2015-11-05 1:48 ` Wangnan (F)
2015-11-05 2:07 ` Wangnan (F)
2015-11-04 2:25 ` [PATCH v2 4/4] perf tools: Improve BPF related error messages output 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=1446603959-233500-1-git-send-email-wangnan0@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.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
all inboxes | Powered by JetHome®