public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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: Re: [PATCH v2 2/3] KVM: x86: add tracepoints to trace mmio begin and complete
Date: Fri, 03 Feb 2012 02:27:22 +0800	[thread overview]
Message-ID: <4F2AD58A.3090307@gmail.com> (raw)
In-Reply-To: <4F2ACE46.4000307@redhat.com>

On 02/03/2012 01:56 AM, Avi Kivity wrote:

> On 02/02/2012 07:55 PM, Xiao Guangrong wrote:
>> On 02/03/2012 01:36 AM, Avi Kivity wrote:
>>
>>> On 02/02/2012 07:27 PM, Xiao Guangrong wrote:
>>>> From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
>>>>
>>>> 'perf kvm-events' will use kvm_exit and kvm_mmio(read...) to calculate
>>>> mmio read emulated time for the old kernel, in order to trace mmio read
>>>> event more exactly, we add kvm_mmio_begin to trace the time when mmio read
>>>> begins
>>>>
>>>> Also, add kvm_mmio_done to trace the time when mmio/pio is completed
>>>
>>> Previously, we discussed using the kvm_entry to do this.  This reduces
>>> the number of tracepoints, and is backwards compatible.  What was the
>>> conclusion?
>>>
>>
>>
>> Since using kvm_entry can cause lots of unnecessary calculated, these new two
>> tracepoints can let the result be exacter.
> 
> Do you have numbers on the ratio between kvm_entry traces and
> kvm_mmio_begin/end traces?
> 


1: Using kvm_mmio_begin/end:

# ./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      54926    58.45%    57.32%      3.90us ( +-   0.29% )
        0xfee00300:W      12906    13.73%    28.70%      8.32us ( +-   0.50% )
        0xfee00300:R      12906    13.73%     7.68%      2.23us ( +-   1.27% )
        0xfee00310:W      12906    13.73%     6.07%      1.76us ( +-   1.05% )
        0xfee00190:R        323     0.34%     0.23%      2.65us ( +-   2.85% )

Total Samples:93967, Total events handled time:374012.26us.

2: kvm_mmio_begin/end is not used:

# ./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      54926    58.45%    42.90%      3.90us ( +-   0.29% )
        0xfee00300:W      12906    13.73%    21.48%      8.32us ( +-   0.50% )
        0xfee00300:R      12906    13.73%    30.26%     11.72us ( +-   1.40% )
        0xfee00310:W      12906    13.73%     4.54%      1.76us ( +-   1.05% )
        0xfee00190:R        323     0.34%     0.82%     12.63us ( +-   2.85% )

Total Samples:93967, Total events handled time:499755.82us.

In this sample, the time of MMIO Read has big different,
in the case 1(new tracepoints), the time is calculated by kvm_mmio_begin -> kvm_mmio(read...)
in the case 2(existing tracepoints), the time is calculated by kvm_exit -> kvm_mmio(read...)

  reply	other threads:[~2012-02-02 18:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 17:25 [PATCH v2] KVM: perf: a smart tool to analyse kvm events Xiao Guangrong
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 [this message]
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=4F2AD58A.3090307@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