linux-kernel - Re: [RFC 0/4] tools lib traceevent: Install fixes

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20180119100728.78ae773f@gandalf.local.home>
Date:   Fri, 19 Jan 2018 10:07:28 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Jiri Olsa <jolsa@...hat.com>
Cc:     Namhyung Kim <namhyung@...nel.org>, Jiri Olsa <jolsa@...nel.org>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        lkml <linux-kernel@...r.kernel.org>,
        David Ahern <dsahern@...il.com>,
        Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [RFC 0/4] tools lib traceevent: Install fixes

On Fri, 19 Jan 2018 11:37:13 +0100
Jiri Olsa <jolsa@...hat.com> wrote:

> hi,
> I checked on this one and was surprised last email is from 2016 ;-)
> so we did not move much with this.. is there still will to do that?
> 
> I think we were kind of waiting for the namespace changes in
> traceevent library.. like to have some common prefix for public
> functions/struct, like 'traceevent_' ?
> 
> thoughts? thanks,

Yes, actually this is back on my radar. I now have full time staff
working on trace-cmd and kernelshark. One of the up coming changes is
to start pushing libtraceevent as a real library which means changing
this.

Thus, do we think "traceevent_" is the proper naming? Could we shorten
it to "tevent_"? Need to get this bike-shedding exercise out of the way
first ;-)

-- Steve