From: David Ahern <dsahern@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] perf test 29 crashing
Date: Thu, 30 Jun 2016 13:41:57 -0600 [thread overview]
Message-ID: <7450cf93-e2dd-ea6e-dfcd-fee2965acab8@gmail.com> (raw)
In-Reply-To: <20160630161816.GA2939@krava>
On 6/30/16 10:18 AM, Jiri Olsa wrote:
> it was the setup in my .perfconfig:
>
> [call-graph]
> threshold=10
>
> caused some of the callchains to disappear and screw the test,
Did you find out why it caused a segfault?
> I think we should make that test using default values, like in
> attached patch
>
> however maybe we should think about disabling ~/.perfconfig
> overload for perf test at all
Agree. The tests need a known config.
next prev parent reply other threads:[~2016-06-30 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 12:34 [BUG] perf test 29 crashing Jiri Olsa
2016-06-28 16:59 ` Arnaldo Carvalho de Melo
2016-06-28 17:52 ` David Ahern
2016-06-29 2:20 ` Namhyung Kim
2016-06-30 15:10 ` Jiri Olsa
2016-06-30 16:18 ` Jiri Olsa
2016-06-30 19:41 ` David Ahern [this message]
2016-07-01 7:02 ` Jiri Olsa
2016-06-30 19:56 ` Arnaldo Carvalho de Melo
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=7450cf93-e2dd-ea6e-dfcd-fee2965acab8@gmail.com \
--to=dsahern@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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 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).