Re: [PATCH 1/8] perf tools: Add '.' as part of the event 'name' token

[Ingo Molnar]

* Stephane Eranian <eranian@xxxxxxxxxx> wrote:

> On Mon, Jan 28, 2013 at 9:52 PM, Stephane Eranian <eranian@xxxxxxxxxx> wrote:
> > Jiri,
> >
> > I don't see part 0/8 of this series. Did you send it to me too?
> >
> > I have some comments about it. I don't see why create something from scratch
> > when I have been developing a library (libpfm4) that takes care of that and that
> > is already used by many tool developers. That library can be linked with perf
> > and provide full symbolic events + all the modifiers. The library is portable
> > and supports all existing archs. It can also be used by self-monitoring apps.
> >
> >
> > You're introducing yet another event table to maintain. And believe me this is
> > a lot of work to maintain this.
> >
> > I don't understand why not use this existing library.
> >
>
> I meant to add that I think it would be more productive if we 
> (you and I) were to work on the library to extend it with 
> external text-based event tables that could be used by perf 
> either directly or thru the libpfm4 interface.

perf is intentionally external file free and does not 
(fundamentally) depend on external libraries either,
other than core system libraries.

There are several advantages to that:

 - there is no version skew and no design/maintenance friction

 - 'upgrading' perf between similar boxes is as simple as
   copying the perf binary

 - it's self-sufficient

 - there's no real advantage of external text files versus
   internal text files (i.e. text tables within the source 
   code), while there are several disadvantages

So as long as Jiri is happy to maintain these tables I think 
it's a superior solution (even if the tables start out 
incomplete), from the perf project's perspective.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/