linux-kernel - Re: [PATCHv2 1/2] perf tools: Collect tracing event data files directly

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:	Wed, 28 Sep 2011 18:56:39 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>, Jiri Olsa <jolsa@...hat.com>,
	acme@...hat.com, eric.dumazet@...il.com, a.p.zijlstra@...llo.nl,
	paulus@...ba.org, linux-kernel@...r.kernel.org,
	nhorman@...driver.com
Subject: Re: [PATCHv2 1/2] perf tools: Collect tracing event data files
 directly


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> > > But it seems Steve's patches are not completely uncontroversial 
> > > because of some crazy disagreements on where the 
> > > libparsevent.so should lay (tools generic or tied to perf).
> > 
> > Which to me seems to be a silly road block, in which I never got 
> > a clear answer for.
> 
> Yeah we need to sort that out with Ingo.

Basically, since it's not at all clear to me where these things (and 
APIs) will go, I'd be much more comfortable with this starting out as 
tools/perf/lib/ - we can still split it out later on. Merging it in 
will be a lot harder.

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/