[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1312666815.18583.221.camel@gandalf.stny.rr.com>
Date: Sat, 06 Aug 2011 17:40:15 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Kyle Moffett <kyle@...fetthome.net>
Cc: Arnaldo Carvalho de Melo <acme@...hat.com>,
Frederic Weisbecker <fweisbec@...il.com>,
David Ahern <dsahern@...il.com>,
Arjan van de Ven <arjan@...radead.org>,
Borislav Petkov <bp@...en8.de>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 0/8] Having perf use libparsevent.a
On Sat, 2011-08-06 at 14:47 -0400, Kyle Moffett wrote:
> On Aug 6, 2011 11:35 AM, "Steven Rostedt" <rostedt@...dmis.org> wrote:
> >
> > On Sat, 2011-08-06 at 09:16 -0600, David Ahern wrote:
> >
> > > If the library is just for parsing trace events why not call it
> > > libtraceparse or libtrace? This isn't perf specific functionality.
> >
> > Actually, I'm thinking libevents would probably be most appropriate.
> It
> > has less to do with perf in general, and more about events. Even
> reading
> > the events goes under this category.
>
> Ooh, please don't... "libevent" is already an epoll() event-based
> application helper library and this would be overly confusing.
OK, what about libkevent, as this has to do with kernel events.
-- 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