From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@amd64.org>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Lin Ming <ming.m.lin@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] perf: Add persistent events
Date: Thu, 17 Jun 2010 12:19:57 -0400 [thread overview]
Message-ID: <1276791597.3556.118.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20100617134357.GA6115@kryptos.osrc.amd.com>
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
next prev parent reply other threads:[~2010-06-17 16:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 19:00 [RFC PATCH 0/2] perf: persistent events prototype Borislav Petkov
2010-05-22 19:00 ` [PATCH 2/2] x86, mce: Make MCE tracepoint persistent event Borislav Petkov
[not found] ` <1274554806-28216-2-git-send-email-bp@alien8.de>
2010-05-23 18:15 ` [PATCH 1/2] perf: Add persistent events Peter Zijlstra
2010-05-23 18:33 ` Borislav Petkov
2010-05-23 18:40 ` Peter Zijlstra
2010-05-23 18:54 ` Borislav Petkov
2010-05-23 19:23 ` Peter Zijlstra
2010-05-25 7:32 ` Borislav Petkov
2010-05-25 14:59 ` Peter Zijlstra
2010-05-28 14:33 ` Ingo Molnar
2010-05-28 15:17 ` Peter Zijlstra
2010-05-28 15:57 ` Borislav Petkov
2010-05-28 18:07 ` Peter Zijlstra
2010-06-03 13:43 ` Borislav Petkov
2010-06-03 17:32 ` Arnaldo Carvalho de Melo
2010-06-03 21:39 ` Borislav Petkov
2010-06-14 19:25 ` Borislav Petkov
2010-06-14 21:01 ` Arnaldo Carvalho de Melo
2010-06-14 21:24 ` Borislav Petkov
2010-06-15 1:02 ` Arnaldo Carvalho de Melo
2010-06-15 10:22 ` Borislav Petkov
2010-06-15 13:22 ` Arnaldo Carvalho de Melo
2010-06-17 13:43 ` Borislav Petkov
2010-06-17 14:25 ` Arnaldo Carvalho de Melo
2010-06-17 15:27 ` Borislav Petkov
2010-06-17 16:19 ` Steven Rostedt [this message]
2010-06-17 17:31 ` Borislav Petkov
2010-05-23 20:36 ` [RFC PATCH 0/2] perf: persistent events prototype Steven Rostedt
2010-05-22 19:04 Borislav Petkov
2010-05-22 19:04 ` [PATCH 1/2] perf: Add persistent events Borislav Petkov
2010-05-22 19:14 ` Borislav Petkov
2010-05-25 3:11 ` Steven Rostedt
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=1276791597.3556.118.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=acme@infradead.org \
--cc=bp@alien8.de \
--cc=bp@amd64.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®