linux-kernel - Re: [PATCH 04/12] perf, x86: Support the TSX intx/intx

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] [day] [month] [year] [list]

Date:	Sun, 3 Feb 2013 11:52:21 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl,
	akpm@...ux-foundation.org, acme@...hat.com, eranian@...gle.com,
	jolsa@...hat.com, namhyung@...nel.org,
	Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 04/12] perf, x86: Support the TSX intx/intx_cp qualifiers
 v3

* Andi Kleen <andi@...stfloor.org> wrote:

> > As requested before, please keep those in a completely 
> > separate series so that minimal support can be merged 
> > upstream. This is
> 
> Hi Ingo, The goal is not to merge "minimal support" but full 
> support.

Stop these idiotic excuses and stop the obstruction already!

Firstly, it is long standing kernel maintenance policy to first 
go for supporting existing applications, ABIs, binaries.

The bulks of your other changes need changes to the ABI and 
changes to tools - and won't be made use of by any of the 
existing installed base of profiling tooling.

It is entirely reasonable and in fact required of me to separate 
out and handle those in a second wave of changes, and this is 
the fourth time you hinder Haswell support by not addressing 
maintainer feedback.

Every other perf contributor understands those concepts.

Secondly, as it's being demonstrated in this discussion again, 
you are a historically problematic contributor who often 
produces avoidably crappy code that needs several iterations to 
get right. You also have a track record of not willing to 
improve and you have a track record of being needlessly 
argumentative and disruptive. All in one, I currently cannot 
trust your code and refuse to handle long, complex patch series 
from you.

Thanks,

	Ingo
--
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/