From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: Wiki docs on counting and tracing KVM perf events
Date: Thu, 13 May 2010 17:57:09 +0300 [thread overview]
Message-ID: <4BEC1345.7040408@redhat.com> (raw)
In-Reply-To: <AANLkTilDjuuZZ3PbdTPJXcz0sDHtTQiASFB1URfsLzB5@mail.gmail.com>
On 05/13/2010 05:35 PM, Stefan Hajnoczi wrote:
> How to count and trace KVM perf events:
>
> http://www.linux-kvm.org/page/Perf_events
>
> I want to draw attention to this because traditional kvm_stat and
> kvm_trace use has been moving over to the debugfs based tracing
> mechanisms. Perhaps we can flesh out documentation and examples of
> common perf event usage.
>
>
Two things are missing to make this really useful:
- a continuously updating difference mode like kvm_stat
- subevents; for example kvm:kvm_exit is an aggregate of all exit types
that can be split using filters to show individual exit reason statistics
The plan is to eventually remove kvm_stat based performance monitoring
in favour of perf events.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-05-13 14:57 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 [this message]
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
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=4BEC1345.7040408@redhat.com \
--to=avi@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.