[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1276791597.3556.118.camel@gandalf.stny.rr.com>
Date: Thu, 17 Jun 2010 12:19:57 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Borislav Petkov <bp@...64.org>
Cc: Arnaldo Carvalho de Melo <acme@...radead.org>,
Borislav Petkov <bp@...en8.de>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...e.hu>,
Frederic Weisbecker <fweisbec@...il.com>,
Lin Ming <ming.m.lin@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] perf: Add persistent events
On Thu, 2010-06-17 at 15:43 +0200, Borislav Petkov wrote:
> > One of the goals at least I have with pursuing this path is to separate
> > out everything that is not strictly 'perf' into things that can be reused
> > by other tools, like yours.
>
> I'm still splitting perf/util into a more or less generic lib.
> Now, I want to reuse as much code as possible and am parsing
> the "mce:mce_record" tracepoint using parse_events(). However,
> this means that I have to push the not-so-generic perf bits
> like util/parse-events.c into the lib. Which, in turn, pulls in
> util/trace-event* etc.
Note, I have a separate generic library in trace-cmd that has the
parsing of trace events as its own library now.
This is the code that started trace-event-parse.c.
It has evolved quite a bit since then. You can get the code from:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
The files are parse-events.c and parse-events.h. As well as some
filtering code: parse-filter.c.
It creates a libparsevent library.
I've been meaning to update the perf stuff with it, but just have not
had the time. Seems that what you are doing might be a good fit for it.
-- 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/
Powered by blists - more mailing lists