linux-kernel - Re: [RFC][PATCH 0/8] Having perf use libparsevent.a

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]

Date:	Fri, 5 Aug 2011 23:24:09 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Borislav Petkov <bp@...en8.de>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [RFC][PATCH 0/8] Having perf use libparsevent.a

* Steven Rostedt <rostedt@...dmis.org> wrote:

> By keeping the code separate from perf, made the transition from 
> trace-cmd to tools much easier. I've wasted too many days trying to 
> get other ways working, and I don't want to rewrite perf to do so.

But we want to move tools together, not further apart. Every code 
activity i see from you is trying to tear apart instrumentation 
tooling - while previously you agreed that it should be unified. So 
why not do tools/perf/lib/ as you agreed before?

I'm really not interested in seeing the libdrm/libdri mess repeated. 
Libraries have their uses when there's some very important external 
interface, but here it's actively harmful as it complicates and 
hardcodes APIs into ABIs that are clearly not finished yet.

Really, lets not be stupid here.

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/