From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: David Ahern <dsahern@gmail.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [RFC][PATCH] KVM: perf: a smart tool to analyse kvm events
Date: Tue, 17 Jan 2012 10:41:00 +0800 [thread overview]
Message-ID: <4F14DFBC.7050908@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F14AA60.1040904@gmail.com>
On 01/17/2012 06:53 AM, David Ahern wrote:
>
>
> On 01/16/2012 02:30 AM, Xiao Guangrong wrote:
>> This tool is very like xenoprof(if i remember correctly), and traces kvm events
>> smartly. currently, it supports vmexit/mmio/ioport events.
>>
>> Usage:
>> - to trace kvm events:
>> # ./perf kvm-events record
>>
>> - show the result
>> # ./perf kvm-events report
>>
>> Some output are as follow:
>> # ./perf kvm-events report
>> Warning: Error: expected type 5 but read 4
>> Warning: Error: expected type 5 but read 0
>> Warning: unknown op '}'
>
> Integrating the trace-cmd plugins into perf will remedy the above errors:
> https://lkml.org/lkml/2011/8/16/352
>
Yes, it is great!
> Unfortunately, that effort is stalled at the moment.
>
>>
>>
>> Analyze events for all VCPUs:
>>
>> VM-EXIT Samples Samples% Time% Avg time
>>
>> APIC_ACCESS 438107 44.89% 6.20% 17.91us
>> EXTERNAL_INTERRUPT 219226 22.46% 8.01% 46.20us
>> IO_INSTRUCTION 122651 12.57% 1.88% 19.44us
>> EPT_VIOLATION 83110 8.52% 1.36% 20.75us
>> PENDING_INTERRUPT 37055 3.80% 0.16% 5.38us
>> CPUID 32718 3.35% 0.08% 3.15us
>> EXCEPTION_NMI 23601 2.42% 0.17% 8.87us
>> HLT 15424 1.58% 82.12% 6735.06us
>> CR_ACCESS 4089 0.42% 0.02% 6.08us
>>
>> Total Samples:975981, Total events handled time:126502464.88us.
>
> Have you thought about dumping a time history -- something similar to
> what perf-script can do with dumping events but adding in kvm-specific
> analysis like what you are doing in these examples?
>
I will look into it and put it to my todo list if it is possible.
Thanks, David!
next prev parent reply other threads:[~2012-01-17 2:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 9:30 [RFC][PATCH] KVM: perf: a smart tool to analyse kvm events Xiao Guangrong
2012-01-16 9:31 ` [PATCH 1/3] KVM: trace mmio read event properly Xiao Guangrong
2012-01-16 10:18 ` Avi Kivity
2012-01-17 2:36 ` Xiao Guangrong
2012-01-16 9:32 ` [PATCH 2/3] KVM: improve trace events of vmexit/mmio/ioport Xiao Guangrong
2012-01-16 9:38 ` Avi Kivity
2012-01-17 2:28 ` Xiao Guangrong
2012-01-17 11:55 ` Marcelo Tosatti
2012-01-17 17:31 ` David Ahern
2012-01-18 2:32 ` Xiao Guangrong
2012-01-18 5:34 ` David Ahern
2012-01-24 12:44 ` Avi Kivity
2012-01-16 9:32 ` [PATCH 3/3] KVM: perf: kvm events analysis tool Xiao Guangrong
2012-01-16 10:04 ` Avi Kivity
2012-01-17 2:30 ` Xiao Guangrong
2012-01-24 12:49 ` Avi Kivity
2012-01-16 10:08 ` Stefan Hajnoczi
2012-01-17 2:37 ` Xiao Guangrong
2012-01-17 11:59 ` Marcelo Tosatti
2012-01-24 12:51 ` Avi Kivity
2012-01-16 10:11 ` [RFC][PATCH] KVM: perf: a smart tool to analyse kvm events Avi Kivity
2012-01-17 2:30 ` Xiao Guangrong
2012-01-16 22:53 ` David Ahern
2012-01-17 2:41 ` Xiao Guangrong [this message]
2012-01-17 4:49 ` David Ahern
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=4F14DFBC.7050908@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=avi@redhat.com \
--cc=dsahern@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.