linux-kernel - Re: [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130813221705.GC19750@two.firstfloor.org>
Date:	Wed, 14 Aug 2013 00:17:05 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Vince Weaver <vince@...ter.net>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Christoph Hellwig <hch@...radead.org>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	Andi Kleen <ak@...ux.intel.com>,
	Namhyung Kim <namhyung.kim@....com>, peterz@...radead.org
Subject: Re: [PATCH] RFC: perf, tools: Move gtk browser into separate
 perfgtk executable

On Tue, Aug 13, 2013 at 05:57:16PM -0400, Vince Weaver wrote:
> On Tue, 13 Aug 2013, Ingo Molnar wrote:
> 
> > 
> > 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.
> 
> Most of the tests in my test-suite are reactive.  Meaning, I wrote them 
> after an ABI-breaking change was reported elsewhere, and I needed a small 
> test case for bisection purposes.  Thus they are good for finding if a 
> corner of the perf ABI re-breaks but they're not great at spotting new 
> breakages.

I guess best would be to just run the major other users (PAPI, perf, trinity, 
numatop, ...?) once around rc1 time.

If it's reported at rc1 things can usually be fixed.

So would just need a easy script to do a quick test of all of these.

-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/