From: Avi Kivity <avi@redhat.com>
To: rostedt@goodmis.org
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Frederic Weisbecker <fweisbec@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Johannes Berg <johannes.berg@intel.com>,
Darren Hart <darren@dvhart.com>
Subject: Re: Perf trace event parse errors for KVM events
Date: Sun, 06 Jun 2010 19:21:59 +0300 [thread overview]
Message-ID: <4C0BCB27.1050601@redhat.com> (raw)
In-Reply-To: <1275836555.15884.83.camel@gandalf.stny.rr.com>
On 06/06/2010 06:02 PM, Steven Rostedt wrote:
> On Sun, 2010-06-06 at 11:08 +0300, Avi Kivity wrote:
>
>
>>> Also, I kicked this off in kernelshark, and it made no difference that I
>>> can see. This is because kernelshark only evaluates the viewable area of
>>> the screen.
>>>
>>>
>> Neat. Can it also search? Where can I find it?<googles, finds, gawks>
>>
>>
> It's in the same repo as trace-cmd:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
>
> I'm still working on it. The latest is in the branch kernelshark-devel.
>
> And yes, it does searches.
>
I'll be tracking it.
In case you're interested in wishlists, my #1 would be to be able to
initiate traces from the GUI (so it's easy to explore the available
trace events and enable them interactively).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-06-06 16:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 12:34 Perf trace event parse errors for KVM events Stefan Hajnoczi
2010-05-28 16:42 ` Stefan Hajnoczi
2010-05-28 21:27 ` Marcelo Tosatti
2010-05-28 21:45 ` Steven Rostedt
2010-05-29 8:21 ` Stefan Hajnoczi
2010-05-29 8:21 ` Stefan Hajnoczi
2010-05-29 11:50 ` Avi Kivity
2010-05-29 13:19 ` Steven Rostedt
2010-05-30 8:10 ` Avi Kivity
2010-05-30 14:03 ` Steven Rostedt
2010-05-30 14:07 ` Avi Kivity
2010-05-30 15:34 ` Steven Rostedt
2010-06-01 8:39 ` Avi Kivity
2010-06-01 11:59 ` Steven Rostedt
2010-06-01 12:39 ` Avi Kivity
2010-06-03 21:57 ` Steven Rostedt
2010-06-06 8:08 ` Avi Kivity
2010-06-06 15:02 ` Steven Rostedt
2010-06-06 16:21 ` Avi Kivity [this message]
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=4C0BCB27.1050601@redhat.com \
--to=avi@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=darren@dvhart.com \
--cc=fweisbec@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=rostedt@goodmis.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.