[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1317229825.4588.12.camel@gandalf.stny.rr.com>
Date: Wed, 28 Sep 2011 13:10:24 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
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
Good to see your email is back :)
On Wed, 2011-09-28 at 18:56 +0200, Ingo Molnar wrote:
> * 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.
I would actually argue that merging is much easier than splitting
something up. If A depends on B, merging B back into A is trivial. But
if B is a part of A, breaking it out of A is a much more difficult task,
as the boundaries of A and B are not so easy to find and the coupling of
the two is much tighter.
I find trying to break things out of perf is very hard to do as the
dependencies are throughout all of perf, and no one seems to agree on
how to do so.
-- Steve
--
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/
Powered by blists - more mailing lists