From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
"David Ahern" <dsahern@gmail.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
HIRAMATU,MASAMI <masami.hiramatsu.pt@hitachi.com>,
"Wang Nan" <wangnan0@huawei.com>,
"Adrian Hunter" <adrian.hunter@intel.com>
Subject: [PATCH 0/7] perf test: Fixes
Date: Thu, 3 Dec 2015 09:34:11 +0100 [thread overview]
Message-ID: <1449131658-1841-1-git-send-email-jolsa@kernel.org> (raw)
hi,
we've got many failing tests, mainly due to commit:
ebe9729c8c31 perf machine: Fix to destroy kernel maps when machine exits
and recent bpf changes, sending fixes.
I think we should force running 'perf test' little more ;-)
thanks,
jirka
---
Jiri Olsa (7):
perf test: Use machine__new_host in dwarf unwind test
perf test: Use machine__new_host in mma thread lookup test
perf test: Use machine__new_host in mma thread code reading test
perf test: Fix cpus and thread maps refference in error path
perf test: Prevent using bpf-output event in round trip name test
perf test: Use machine__new_host in thread mg sharing test
perf test: Create kernel maps properly for hist entries test
tools/perf/tests/code-reading.c | 14 +++++++++-----
tools/perf/tests/dwarf-unwind.c | 8 ++------
tools/perf/tests/evsel-roundtrip-name.c | 11 +++++------
tools/perf/tests/hists_common.c | 7 +++++++
tools/perf/tests/mmap-thread-lookup.c | 6 ++----
tools/perf/tests/thread-mg-share.c | 7 +++----
6 files changed, 28 insertions(+), 25 deletions(-)
next reply other threads:[~2015-12-03 8:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 8:34 Jiri Olsa [this message]
2015-12-03 8:34 ` [PATCH 1/7] perf test: Use machine__new_host in dwarf unwind test Jiri Olsa
2015-12-08 4:31 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-03 8:34 ` [PATCH 2/7] perf test: Use machine__new_host in mma thread lookup test Jiri Olsa
2015-12-04 13:22 ` Namhyung Kim
2015-12-06 16:05 ` Jiri Olsa
2015-12-08 4:31 ` [tip:perf/core] perf test: Use machine__new_host in mmap " tip-bot for Jiri Olsa
2015-12-03 8:34 ` [PATCH 3/7] perf test: Use machine__new_host in mma thread code reading test Jiri Olsa
2015-12-08 4:31 ` [tip:perf/core] perf test: Use machine__new_host in mmap " tip-bot for Jiri Olsa
2015-12-03 8:34 ` [PATCH 4/7] perf test: Fix cpus and thread maps refference in error path Jiri Olsa
2015-12-08 4:32 ` [tip:perf/core] perf test: Fix cpus and thread maps reference " tip-bot for Jiri Olsa
2015-12-03 8:34 ` [PATCH 5/7] perf test: Prevent using bpf-output event in round trip name test Jiri Olsa
2015-12-08 4:32 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-03 8:34 ` [PATCH 6/7] perf test: Use machine__new_host in thread mg sharing test Jiri Olsa
2015-12-03 8:34 ` [PATCH 7/7] perf test: Create kernel maps properly for hist entries test Jiri Olsa
2015-12-04 13:23 ` Namhyung Kim
2015-12-06 16:07 ` [PATCHv2 " Jiri Olsa
2015-12-03 9:09 ` [PATCH 0/7] perf test: Fixes Jiri Olsa
2015-12-04 13:26 ` Namhyung Kim
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=1449131658-1841-1-git-send-email-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--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).