From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: Vince Weaver <vince@deater.net>,
Christoph Hellwig <hch@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Namhyung Kim <namhyung.kim@lge.com>,
peterz@infradead.org
Subject: Re: [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable
Date: Tue, 13 Aug 2013 09:11:41 -0300 [thread overview]
Message-ID: <20130813121141.GB2188@ghostprotocols.net> (raw)
In-Reply-To: <20130813104821.GB2170@gmail.com>
Em Tue, Aug 13, 2013 at 12:48:21PM +0200, Ingo Molnar escreveu:
> To resolve this situation you could help us out by doing either of these:
> 1) integrate your tests into tools/, there's 'perf test' that has a ton
> of testcases already
I think Jiri is working on merging some of those tests, Jiri?
Yeah, these at least:
commit 06933e3a732bb305b0721f1051a45264588e0519
Author: Jiri Olsa <jolsa@redhat.com>
Date: Sun Mar 10 19:41:11 2013 +0100
perf tests: Test breakpoint overflow signal handler counts
commit 5a6bef47b418676546ab86d25631c3cfb9ffaf2a
Author: Jiri Olsa <jolsa@redhat.com>
Date: Sun Mar 10 19:41:10 2013 +0100
perf tests: Test breakpoint overflow signal handler
> 2) run your testsuite more frequently - instead of waiting for a stable
> kernel to be released and then complain about breakage.
My feeling is that he increased the frequency of such tests.
> So far you refused to do any of this and blamed others for non-reported
> breakages :-/
He has been using the perf trinity fuzzer and reporting problems, thanks
Vince!
- Arnaldo
next prev parent reply other threads:[~2013-08-13 12:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 2:22 [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable Andi Kleen
2013-08-05 8:16 ` Ingo Molnar
2013-08-05 8:23 ` Christoph Hellwig
2013-08-05 8:31 ` Ingo Molnar
2013-08-05 8:34 ` Christoph Hellwig
2013-08-05 9:08 ` Ingo Molnar
2013-08-06 6:19 ` Christoph Hellwig
2013-08-12 18:19 ` Ingo Molnar
2013-08-12 19:25 ` Vince Weaver
2013-08-13 10:48 ` Ingo Molnar
2013-08-13 12:11 ` Arnaldo Carvalho de Melo [this message]
2013-08-13 16:00 ` Ingo Molnar
2013-08-13 21:57 ` Vince Weaver
2013-08-13 22:17 ` Andi Kleen
2013-08-14 14:13 ` Arnaldo Carvalho de Melo
2013-08-14 14:20 ` Ingo Molnar
2013-08-13 14:03 ` Vince Weaver
2013-08-13 16:04 ` Ingo Molnar
2013-08-05 9:08 ` Namhyung Kim
2013-08-05 9:12 ` Ingo Molnar
2013-08-05 9:18 ` Pekka Enberg
2013-08-05 19:10 ` Andi Kleen
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=20130813121141.GB2188@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=peterz@infradead.org \
--cc=vince@deater.net \
/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