[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120425163738.GE17992@infradead.org>
Date: Wed, 25 Apr 2012 13:37:38 -0300
From: Arnaldo Carvalho de Melo <acme@...radead.org>
To: "Frank Ch. Eigler" <fche@...hat.com>
Cc: Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
Namhyung Kim <namhyung.kim@....com>,
Jiri Olsa <jolsa@...hat.com>, Arun Sharma <asharma@...com>,
Michael Rubin <mrubin@...gle.com>,
David Sharp <dhsharp@...gle.com>,
Vaibhav Nagarnaik <vnagarnaik@...gle.com>,
Julia Lawall <julia@...u.dk>, Tom Zanussi <tzanussi@...il.com>
Subject: Re: Our failure on tracing tools unification
Em Wed, Apr 25, 2012 at 10:19:35AM -0400, Frank Ch. Eigler escreveu:
>
> mingo wrote:
>
> > [...] One thing that would suck is perf being bound by various
> > versions of this library floating out there.
>
> Could the event parser shared library be ABI-preserving? If so, what
> would perf have to fear?
Perhaps its because people working on perf grew in the kernel, where we
can change things as we see fit, i.e. change the networking API? Sure,
we can go over the drivers and change them, its all in the same source
tree, etc.
> > [...] We had nothing but pain from external libraries so far [...]
>
> If the elfutils, newt, gtk, bfd, iberty, zlib, python libraries didn't
> contribute useful and un-rewriteable functionality, perf would not be
> using them.
newt was a pain and will go away, 99% of things rely just on libslang,
but even that one could go, bfd we use just for C++ demangling, so
probably could go too.
- Arnaldo
--
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