From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.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>,
David Ahern <dsahern@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: [PATCH v4 0/3] KVM: perf: kvm events analysis tool
Date: Thu, 09 Feb 2012 17:06:50 +0800 [thread overview]
Message-ID: <4F338CAA.10807@linux.vnet.ibm.com> (raw)
Changlog:
There are some changes from David Ahern's review:
- let the tool to be off-box analysis by getting cpu isa
from HEADER_CPUID feature and removing max-vcpu related code.
- attach per vcpu record structure to the thread by adding a void pointer
in "struct thread".
- remove unnecessary tool argument(-v).
The output example is following:
# ./perf kvm-events report --event mmio --vcpu 3
Warning: Error: expected type 5 but read 4
Warning: Error: expected type 5 but read 0
Warning: unknown op '}'
Analyze events for VCPU 3:
MMIO Access Samples Samples% Time% Avg time
0xfee00380:W 45534 78.00% 84.76% 5.27us ( +- 0.77% )
0xfee00300:W 4280 7.33% 9.37% 6.20us ( +- 1.91% )
0xfee00300:R 4280 7.33% 3.34% 2.21us ( +- 1.53% )
0xfee00310:W 4280 7.33% 2.52% 1.67us ( +- 0.71% )
Total Samples:58374, Total events handled time:283257.68us.
next reply other threads:[~2012-02-09 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 9:06 Xiao Guangrong [this message]
2012-02-09 9:07 ` [PATCH 1/3] KVM: x86: export svm/vmx exit code and vector code to userspace Xiao Guangrong
2012-02-09 9:08 ` [PATCH 2/3] KVM: x86: add tracepoints to trace mmio begin and complete Xiao Guangrong
2012-02-09 9:09 ` [PATCH 3/3] KVM: perf: kvm events analysis tool Xiao Guangrong
2012-02-13 3:04 ` David Ahern
2012-02-13 5:00 ` Xiao Guangrong
2012-02-20 23:47 ` David Ahern
2012-02-21 3:52 ` Xiao Guangrong
2012-02-21 4:58 ` David Ahern
2012-02-27 4:57 ` 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=4F338CAA.10807@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=acme@infradead.org \
--cc=avi@redhat.com \
--cc=dsahern@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.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.