[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140626073605.GB1177@krava.brq.redhat.com>
Date: Thu, 26 Jun 2014 09:36:05 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Arnaldo Carvalho de Melo <acme@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Robert Richter <rric@...nel.org>,
David Ahern <dsahern@...il.com>,
Namhyung Kim <namhyung@...il.com>,
Jean Pihet <jean.pihet@...aro.org>
Subject: Re: [PATCH] perf tool: Carve out ctype.h et al
On Wed, Jun 25, 2014 at 10:11:47PM +0200, Borislav Petkov wrote:
> On Wed, Jun 25, 2014 at 04:42:54PM -0300, Arnaldo Carvalho de Melo wrote:
> > Probably will come in a separate patchkit that is dependent on this,
> > but not strictly related?
>
> Yeah, so roughly speaking, we want to carve out the code which opens and
> handles events in perf tool so that we can use it in other tools. In the
this functionality is inside evlist/evsel/target(...) objects
> particular example with the ras daemon, we want to be able to open a
> tracepoint in userspace and read from it.
the ras daemon is not in tree yet is it? cant find it..
>
> We're doing this piecewise because perf tool changes too fast and I've
> done a full conversion patchset a couple of times already only to
> realize that it grows obsolete practically only days after sending it
> out. (Btw, for that it is all your fault, of course :-P). Which makes
> preparing a full patchset almost impossible.
>
> Does this explanation make sense?
I think we should librarize only stuff we will share. Whats the plan
about the ras daemon (if I did not overlook it) to be put into tools?
thanks,
jirka
--
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/
Powered by blists - more mailing lists