All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: 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:30:59 +0800	[thread overview]
Message-ID: <4F14DD63.3010901@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F13F7EB.3060108@redhat.com>

On 01/16/2012 06:11 PM, Avi Kivity wrote:


>> Total Samples:975981, Total events handled time:126502464.88us.
> 
> Nice!  If we can have a live version as well, this can replace kvm_stat.
> 
> The average numbers are really high.  Like a factor of 3x-4x off.  Would
> be good to print the standard deviation and see why.  Maybe it's due to
> the tracing overhead.
> 


It is a good suggestion, i will print stddev in the next version.

>> The default event to be analysed is vmexit, we can use --event to specify it,
>> for example, if we want to trace mmio event:
>> # ./perf kvm-events report --event mmio
>>   Warning: Error: expected type 5 but read 4
>>   Warning: Error: expected type 5 but read 0
>>   Warning: unknown op '}'
>>
>>
>> Analyze events for all VCPUs:
>>
>>          MMIO Access    Samples      Samples%         Time%        Avg time
>>
>>         0xfee00380:W     196589        64.95%        70.01%         3.83us
>>         0xfee00310:W      35356        11.68%         6.48%         1.97us
>>         0xfee00300:W      35356        11.68%        16.37%         4.97us
>>         0xfee00300:R      35356        11.68%         7.14%         2.17us
> 
> These are more reasonable (though still high - 5us for an ICR write?)
> 


Hmm, maybe i need look into it...

>> Total Samples:975981, Total events handled time:126502464.88us.
>>
>> I hope guys will like it and any comments are welcome! :)
> 
> I think it's great!  A live version would be a nice addition too.
> 
> Please copy the perf userspace maintainers to get more detailed review
> in the next version.
> 


Okay, Thanks!

  reply	other threads:[~2012-01-17  2:30 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 [this message]
2012-01-16 22:53 ` David Ahern
2012-01-17  2:41   ` Xiao Guangrong
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=4F14DD63.3010901@linux.vnet.ibm.com \
    --to=xiaoguangrong@linux.vnet.ibm.com \
    --cc=avi@redhat.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.