From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Wiki docs on counting and tracing KVM perf events
Date: Thu, 20 May 2010 15:37:53 +0300 [thread overview]
Message-ID: <4BF52D21.6090407@redhat.com> (raw)
In-Reply-To: <AANLkTim2tmMX-lo45fEpeSUTvw2K1BAgxN-gcDDDNCEJ@mail.gmail.com>
On 05/20/2010 03:24 PM, Stefan Hajnoczi wrote:
> On Thu, May 20, 2010 at 1:14 PM, Avi Kivity<avi@redhat.com> wrote:
>
>>> echo 1>/sys/kernel/debug/tracing/events/kvm/enable
>>> cat /sys/kernel/debug/tracing/trace_pipe>results/trace&
>>>
>> perf will enable the events by itself (no?), so all you need is is the perf
>> call in the middle.
>>
> Yes, it will enable events. However, I am also generating a
> kvm_trace-like log using trace_pipe. On this box I couldn't get perf
> trace working so I used trace_pipe for the kvm_trace-equivalent and
> perf stat for the kvm_stat equivalent.
>
Ah. There's the new shiny trace_cmd as well.
If you're getting a (binary) trace, runing perf stat is redundant since
it contains the same data.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2010-05-20 12:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 14:35 Wiki docs on counting and tracing KVM perf events Stefan Hajnoczi
2010-05-13 14:57 ` Avi Kivity
2010-05-20 8:15 ` Jes Sorensen
2010-05-20 8:19 ` Avi Kivity
2010-05-20 8:24 ` Jes Sorensen
2010-05-20 11:05 ` Stefan Hajnoczi
2010-05-20 11:10 ` Avi Kivity
2010-05-20 11:16 ` Jes Sorensen
2010-05-20 11:23 ` Stefan Hajnoczi
2010-05-20 12:14 ` Avi Kivity
2010-05-20 12:24 ` Stefan Hajnoczi
2010-05-20 12:37 ` 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=4BF52D21.6090407@redhat.com \
--to=avi@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=stefanha@gmail.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.