From: Xiao Guangrong <xiaoguangrong.eric@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: [PATCH v2] KVM: perf: a smart tool to analyse kvm events
Date: Fri, 03 Feb 2012 01:25:27 +0800 [thread overview]
Message-ID: <4F2AC707.7020801@gmail.com> (raw)
Changlog:
- calculate stddev.
- make it works both for old kernel and new kernel.
- dynamically inquire max vcpus and cpu isa.
This is a example result of vmexit:
# ./perf kvm-events report
Warning: Error: expected type 5 but read 4
Warning: Error: expected type 5 but read 0
Warning: unknown op '}'
Analyze events for all VCPUs:
VM-EXIT Samples Samples% Time% Avg time
APIC_ACCESS 152367 34.07% 1.74% 15.69us ( +- 2.02% )
IO_INSTRUCTION 142663 31.90% 1.76% 16.91us ( +- 2.87% )
HLT 46681 10.44% 95.87% 2816.04us ( +- 2.94% )
EPT_VIOLATION 40184 8.98% 0.15% 5.17us ( +- 1.26% )
CPUID 21284 4.76% 0.04% 2.47us ( +- 0.66% )
EXTERNAL_INTERRUPT 21215 4.74% 0.36% 23.39us ( +- 2.83% )
EXCEPTION_NMI 11723 2.62% 0.04% 5.21us ( +- 2.46% )
CR_ACCESS 5810 1.30% 0.02% 5.06us ( +- 1.01% )
PENDING_INTERRUPT 5322 1.19% 0.01% 3.69us ( +- 1.73% )
Total Samples:447249, Total events handled time:137125528.85us.
Any comments are welcome! :)
next reply other threads:[~2012-02-02 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 17:25 Xiao Guangrong [this message]
2012-02-02 17:26 ` [PATCH v2 1/3] KVM: x86: move kvm_exit related definitions into kvm_exit.h Xiao Guangrong
2012-02-02 17:30 ` Avi Kivity
2012-02-02 17:48 ` Xiao Guangrong
2012-02-02 17:27 ` [PATCH v2 2/3] KVM: x86: add tracepoints to trace mmio begin and complete Xiao Guangrong
2012-02-02 17:36 ` Avi Kivity
2012-02-02 17:55 ` Xiao Guangrong
2012-02-02 17:56 ` Avi Kivity
2012-02-02 18:27 ` Xiao Guangrong
2012-02-02 18:43 ` Xiao Guangrong
2012-02-02 17:28 ` [PATCH v2 3/3] KVM: perf: kvm events analysis tool Xiao Guangrong
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=4F2AC707.7020801@gmail.com \
--to=xiaoguangrong.eric@gmail.com \
--cc=acme@infradead.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).