lkml.org 
[lkml]   [2013]   [Aug]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable

* Arnaldo Carvalho de Melo <acme@ghostprotocols.net> wrote:

> 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!

Absolutely, it's much appreciated, thanks Vince!

I was reacting to this claim:

> > I've had perf ABI changes break programs I maintain at least three
> > times in the last 2 kernel releases.

that can only be addressed by either extending 'perf test' or by testing
libpfm et al sooner. The upstream kernel can only address regressions that
get reported.

Thanks,

Ingo


\
 
 \ /
  Last update: 2013-08-13 19:01    [W:0.155 / U:1.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site