From: Steven Rostedt <rostedt@goodmis.org>
To: Kyle Moffett <kyle@moffetthome.net>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
David Ahern <dsahern@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/8] Having perf use libparsevent.a
Date: Sat, 06 Aug 2011 17:40:15 -0400 [thread overview]
Message-ID: <1312666815.18583.221.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <CAGZ=bq+mJ-9pf0Y22b9LLey0Em2Y7SAA5FnQ5cPsde6GB_aqgw@mail.gmail.com>
On Sat, 2011-08-06 at 14:47 -0400, Kyle Moffett wrote:
> On Aug 6, 2011 11:35 AM, "Steven Rostedt" <rostedt@goodmis.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
next parent reply other threads:[~2011-08-06 21:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGZ=bq+mJ-9pf0Y22b9LLey0Em2Y7SAA5FnQ5cPsde6GB_aqgw@mail.gmail.com>
2011-08-06 21:40 ` Steven Rostedt [this message]
2011-08-06 23:14 ` Kyle Moffett
2011-08-08 9:34 ` Américo Wang
2011-08-08 13:42 ` Steven Rostedt
2011-08-05 20:59 Steven Rostedt
2011-08-05 21:24 ` Ingo Molnar
2011-08-06 0:43 ` Frederic Weisbecker
2011-08-06 6:48 ` Ingo Molnar
2011-08-06 14:56 ` Frederic Weisbecker
[not found] ` <CAKYOsXw+Q+h2D++LxAoCUJ3tFVEhczBgDWNjwXzuJ0mNDav_Rw@mail.gmail.com>
2011-08-06 15:18 ` Frederic Weisbecker
2011-08-06 15:35 ` Steven Rostedt
2011-08-06 1:01 ` Steven Rostedt
2011-08-06 6:51 ` Ingo Molnar
2011-08-08 21:30 ` Steven Rostedt
2011-08-06 9:14 ` Borislav Petkov
2011-08-06 0:07 ` David Ahern
2011-08-06 1:05 ` Steven Rostedt
2011-08-06 15:23 ` Colin Walters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1312666815.18583.221.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=arjan@infradead.org \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=kyle@moffetthome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®