linux-kernel - Re: [PATCH] perf: Move fs.* to generic lib/lk/

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]

Date:	Thu, 21 Nov 2013 12:12:58 -0300
From:	Arnaldo Carvalho de Melo <acme@...radead.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Borislav Petkov <bp@...e.de>, Jiri Olsa <jolsa@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Robert Richter <rric@...nel.org>
Subject: Re: [PATCH] perf: Move fs.* to generic lib/lk/

Em Thu, Nov 21, 2013 at 07:39:55AM -0500, Steven Rostedt escreveu:
> On Thu, Nov 21, 2013 at 01:06:05PM +0100, Borislav Petkov wrote:
> > No, I absolutely don't think it is a bikeshedding exercise too. We
> > really need that lib because people have started growing their own
> > facilities in tools/ and outside so having a lib which implements
> > generic functionality for interfacing with the kernel right is going to
> > save everyone a lot of time and energy.

> Should we put libtraceevent here too? Have all kapi functionality live here?

Don't know, what I'm liking about this discussion now is that we're
focusing on breaking it down into multiple libraries.

So at some point, symbol resolution, that involves parsing multiple "fs
based kernel api" (/proc/{kallsyms,modules,etc), but should not be in
the library being discussed now, will be another tools/perf/util/
"spin-off", that, again, focuses on a clear mission statement and is
useful for multiple /usr/src/linux/tools/ "clients".

And as the first step, only tools/ clients would be targeted, as we
would have some time to do changes that touches the libraries _and_ all
its users, just like we can do with kernel APIs and its users, i.e.
drivers, etc.

Only at a later stage, when those libraries are boringly mature, we
would export them for wider use.

> As libtraceevent is getting mature, we need to get it out as a real library
> soon. There is already three utilities that use it: perf, trace-cmd and 
> powertop. And I've heard of others that want that functionatity.
> 
> -- 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/