linux-kernel - Re: [RFC][PATCH 0/8] Having perf use libparsevent.a

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 6 Aug 2011 19:14:13 -0400
From:	Kyle Moffett <kyle@...fetthome.net>
To:	Steven Rostedt <rostedt@...dmis.org>
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, Aug 6, 2011 at 17:40, Steven Rostedt <rostedt@...dmis.org> wrote:
> 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.

Hmm, well "kevent()" is a BSD syscall that does the same kinds of things
as "epoll()" does on Linux.  It's used by libevent, in fact.

Maybe "libkernevent"?  A quick google doesn't find anything problematic
there...  Other options with minimal chance of confusion are:
  libkernelevent
  liblinuxevent
  libinuxevent (Linked with option "-linuxevent")

To be honest I don't really see anything wrong with a name involving
"trace"...  Perhaps something like libevtrace/libtraceevent/etc?

Cheers,
Kyle Moffett
--
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/