From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
Jiri Olsa <jolsa@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Robert Richter <rric@kernel.org>
Subject: Re: [PATCH] perf: Move fs.* to generic lib/lk/
Date: Thu, 21 Nov 2013 12:12:58 -0300 [thread overview]
Message-ID: <20131121151258.GB24806@ghostprotocols.net> (raw)
In-Reply-To: <20131121123954.GA8044@home.goodmis.org>
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
next prev parent reply other threads:[~2013-11-21 15:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 21:56 [PATCH] perf: Move fs.* to generic lib/lk/ Borislav Petkov
2013-11-21 7:34 ` Ingo Molnar
2013-11-21 10:07 ` Borislav Petkov
2013-11-21 11:17 ` Ingo Molnar
2013-11-21 11:30 ` Borislav Petkov
2013-11-21 11:42 ` Ingo Molnar
2013-11-21 12:06 ` Borislav Petkov
2013-11-21 12:39 ` Steven Rostedt
2013-11-21 13:49 ` Borislav Petkov
2013-11-21 13:56 ` Steven Rostedt
2013-11-21 14:18 ` Borislav Petkov
2013-11-21 15:12 ` Arnaldo Carvalho de Melo [this message]
2013-11-21 15:05 ` Arnaldo Carvalho de Melo
2013-11-21 15:28 ` Borislav Petkov
2013-11-21 17:37 ` Arnaldo Carvalho de Melo
2013-11-21 19:00 ` Borislav Petkov
2013-11-22 12:27 ` Ingo Molnar
2013-11-22 13:50 ` Borislav Petkov
2013-11-22 15:00 ` Arnaldo Carvalho de Melo
2013-11-22 15:20 ` David Ahern
2013-11-22 15:39 ` Ingo Molnar
2013-11-22 15:54 ` Ingo Molnar
2013-11-23 13:12 ` Borislav Petkov
2013-11-26 18:03 ` Ingo Molnar
2013-11-27 15:42 ` Borislav Petkov
2013-11-23 13:04 ` Borislav Petkov
2013-11-26 18:17 ` Ingo Molnar
2013-11-27 15:39 ` Borislav Petkov
2013-11-28 12:16 ` Borislav Petkov
2013-12-02 20:30 ` Arnaldo Carvalho de Melo
2013-11-22 14:57 ` Arnaldo Carvalho de Melo
2013-11-22 15:43 ` Ingo Molnar
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=20131121151258.GB24806@ghostprotocols.net \
--to=acme@infradead.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rric@kernel.org \
/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