From: Hemant Kumar <hemant@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: maddy@linux.vnet.ibm.com, srikar@linux.vnet.ibm.com,
peterz@infradead.org, linux-kernel@vger.kernel.org,
acme@kernel.org, paulus@samba.org, warrier@linux.vnet.ibm.com,
mingo@kernel.org
Subject: [PATCH v2 0/5] KVM events analysis on powerpc with perf
Date: Mon, 20 Apr 2015 20:32:10 +0530 [thread overview]
Message-ID: <1429542135-10632-1-git-send-email-hemant@linux.vnet.ibm.com> (raw)
Hello!
This patchset enables "perf kvm stat record/report" on powerpc,
which can be used to analyze certain KVM events : KVM exits and
hypervisor calls. The statistics can be shown individually for
each running VM in the host and hence, can be useful in giving
an idea of the performance of a VM on a certain workload.
Example usages are shown in each of the patches individually.
Here is a sample output :
Analyze events for pid(s) 60515, all VCPUs:
VM-EXIT Samples Samples% Time% Min Time Max Time Avg time
H_DATA_STORAGE 5006 35.30% 0.13% 1.94us 49.46us 12.37us ( +- 0.52% )
HV_DECREMENTER 4457 31.43% 0.02% 0.72us 16.14us 1.91us ( +- 0.96% )
SYSCALL 2690 18.97% 0.10% 2.84us 528.24us 18.29us ( +- 3.75% )
RETURN_TO_HOST 1789 12.61% 99.76% 1.58us 672791.91us 27470.23us ( +- 3.00% )
EXTERNAL 240 1.69% 0.00% 0.69us 10.67us 1.33us ( +- 5.34% )
Total Samples:14182, Total events handled time:49264158.30us.
The above example shows how many number of kvm exits have happened
during a certain period of time. Along with the total number of exits,
it also groups all the exits based on their reasons. Frequency for
individual exit reasons is also shown.
This patchset makes use of kvm_hv tracepoints and enables "perf kvm
stat record" to trace on them. After recording, "perf kvm stat report"
does all the post processing of parsing the events captured and
classifying them according to their exit reasons (which are already
availabe in "trace_book3s.h"). Similar method is used with hcall
analysis.
Thanks,
Hemant Kumar
next reply other threads:[~2015-04-20 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 15:02 Hemant Kumar [this message]
2015-04-20 15:02 ` [PATCH v2 1/5] kvm/powerpc: Export exit reasons as uapi Hemant Kumar
2015-04-20 15:02 ` [PATCH v2 2/5] kvm/powerpc: Add exit reason for return code 0x0 Hemant Kumar
2015-04-20 15:02 ` [PATCH v2 3/5] perf/kvm: KVM exit events analysis Hemant Kumar
2015-04-20 15:02 ` [PATCH v2 4/5] kvm/powerpc: Move HCALL reason codes to uapi Hemant Kumar
2015-04-20 15:02 ` [PATCH v2 5/5] perf/kvm: HCALL events analysis Hemant Kumar
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=1429542135-10632-1-git-send-email-hemant@linux.vnet.ibm.com \
--to=hemant@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=warrier@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 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).