From: Steven Rostedt <rostedt@goodmis.org>
To: David Ahern <dsahern@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [RFC][PATCH 0/8] Having perf use libparsevent.a
Date: Fri, 05 Aug 2011 21:05:19 -0400 [thread overview]
Message-ID: <1312592719.18583.219.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4E3C85B0.7090905@gmail.com>
On Fri, 2011-08-05 at 18:07 -0600, David Ahern wrote:
> On 08/05/2011 02:59 PM, Steven Rostedt wrote:
> > Hi All,
> >
> > I've spent the week working on getting libparsevent.a working with
> > perf. After several rewrites, hacking in both perf and the trace-cmd
> > code, and breaking both beyond repair, I finally got to a point that
> > it just works.
>
> Does this version allow use of the trace-cmd plugins with perf?
> Specifically, kvm tracing is not compatible with perf (perf barfs on the
> kvm_exit traces); I suspect the plugins would fix that - as well as have
> the pretty format for the exit reasons.
>
> I want to try out the patch set, but will not have time until the week
> of the kvm forum/linuxcon.
>
I posted this patch set as an RFC as I don't have time to waste on doing
more work, and I knew it would cause some controversy.
That said, this patch set does not yet add the plugins, but it lays the
ground work for adding plugins to perf in the next step. I probably
could get plugins working with perf by next week. If we keep going in
this direction, otherwise, probably not till next year.
-- Steve
next prev parent reply other threads:[~2011-08-06 1:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 20:59 Steven Rostedt
2011-08-05 20:59 ` [RFC][PATCH 1/8] perf: Separate out trace-cmd parse-events from perf files Steven Rostedt
2011-08-15 16:14 ` David Ahern
2011-08-15 16:22 ` Steven Rostedt
2011-08-17 0:08 ` David Ahern
2011-08-17 0:31 ` Steven Rostedt
2011-08-18 13:51 ` Frederic Weisbecker
2011-08-18 16:37 ` David Ahern
2011-08-18 16:59 ` Steven Rostedt
2011-08-05 20:59 ` [RFC][PATCH 2/8] tools/events: Add files to create libparsevent.a Steven Rostedt
2011-08-05 20:59 ` [RFC][PATCH 3/8] perf: Build libparsevent.a Steven Rostedt
2011-08-05 20:59 ` [RFC][PATCH 4/8] events: Update tools/lib/events to work with perf Steven Rostedt
2011-08-05 20:59 ` [RFC][PATCH 5/8] perf: Have perf use the new libparsevent.a library Steven Rostedt
2011-08-05 20:59 ` [RFC][PATCH 6/8] perf/events: Add flag to produce nsec output Steven Rostedt
2011-08-05 20:59 ` [RFC][PATCH 7/8] perf/events: Add flag/symbol format_flags Steven Rostedt
2011-08-05 20:59 ` [RFC][PATCH 8/8] perf/events: Correct size given to memset Steven Rostedt
2011-08-05 21:24 ` [RFC][PATCH 0/8] Having perf use libparsevent.a Ingo Molnar
2011-08-06 0:43 ` Frederic Weisbecker
2011-08-06 6:48 ` Ingo Molnar
2011-08-06 14:56 ` Frederic Weisbecker
[not found] ` <CAKYOsXw+Q+h2D++LxAoCUJ3tFVEhczBgDWNjwXzuJ0mNDav_Rw@mail.gmail.com>
2011-08-06 15:18 ` Frederic Weisbecker
2011-08-06 15:35 ` Steven Rostedt
2011-08-06 1:01 ` Steven Rostedt
2011-08-06 6:51 ` Ingo Molnar
2011-08-08 21:30 ` Steven Rostedt
2011-08-06 9:14 ` Borislav Petkov
2011-08-06 0:07 ` David Ahern
2011-08-06 1:05 ` Steven Rostedt [this message]
2011-08-06 15:23 ` Colin Walters
[not found] <CAGZ=bq+mJ-9pf0Y22b9LLey0Em2Y7SAA5FnQ5cPsde6GB_aqgw@mail.gmail.com>
2011-08-06 21:40 ` Steven Rostedt
2011-08-06 23:14 ` Kyle Moffett
2011-08-08 9:34 ` Américo Wang
2011-08-08 13:42 ` 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=1312592719.18583.219.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=arjan@infradead.org \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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®