From: "Hailong Yang" <hailong.yang1115@gmail.com>
To: <kvm@vger.kernel.org>
Subject: FW: Descriptions about KVM performance counters
Date: Wed, 16 May 2012 20:11:21 +0800 [thread overview]
Message-ID: <4fb3996f.2c75440a.2bee.4d8b@mx.google.com> (raw)
Anyone please commits or provides any useful insights? Really appreciate~
Hailong
> -----Original Message-----
> From: Hailong Yang [mailto:hailong.yang1115@gmail.com]
> Sent: Tuesday, May 15, 2012 6:48 PM
> To: kvm@vger.kernel.org
> Subject: Descriptions about KVM performance counters
>
> Dear all,
>
> Is there a brief description or any document about the meanings of kvm
> performance events traced by 'perf' command? Some of events are hard to
> guess what they are standing for. And also is there any correlation or
exact
> mapping between the output of 'kvm_stat' and the perf kvm events? Another
> question is, since the kvm guest vm is executed as a user level process,
does
> that mean I can only account for the user level performance events when I
am
> trying to profile the performance of guest VM with 'perf' command?
>
> [root@dell06 ~]# perf list | grep kvm
> kvmmmu:kvm_mmu_pagetable_walk [Tracepoint
> event]
> kvmmmu:kvm_mmu_paging_element [Tracepoint
> event]
> kvmmmu:kvm_mmu_set_accessed_bit [Tracepoint
> event]
> kvmmmu:kvm_mmu_set_dirty_bit [Tracepoint
> event]
> kvmmmu:kvm_mmu_walker_error [Tracepoint
> event]
> kvmmmu:kvm_mmu_get_page
> [Tracepoint event]
> kvmmmu:kvm_mmu_sync_page [Tracepoint
> event]
> kvmmmu:kvm_mmu_unsync_page [Tracepoint
> event]
> kvmmmu:kvm_mmu_zap_page
> [Tracepoint event]
> kvm:kvm_entry [Tracepoint
> event]
> kvm:kvm_hypercall [Tracepoint
> event]
> kvm:kvm_pio [Tracepoint
> event]
> kvm:kvm_cpuid [Tracepoint
> event]
> kvm:kvm_apic [Tracepoint
> event]
> kvm:kvm_exit [Tracepoint
> event]
> kvm:kvm_inj_virq [Tracepoint
> event]
> kvm:kvm_inj_exception [Tracepoint
> event]
> kvm:kvm_page_fault [Tracepoint
> event]
> kvm:kvm_msr [Tracepoint
> event]
> kvm:kvm_cr [Tracepoint
> event]
> kvm:kvm_pic_set_irq [Tracepoint
> event]
> kvm:kvm_apic_ipi [Tracepoint
> event]
> kvm:kvm_apic_accept_irq [Tracepoint
> event]
> kvm:kvm_set_irq [Tracepoint
> event]
> kvm:kvm_ioapic_set_irq [Tracepoint
> event]
> kvm:kvm_msi_set_irq [Tracepoint
> event]
> kvm:kvm_ack_irq [Tracepoint
> event]
> kvm:kvm_mmio [Tracepoint
> event]
>
> [root@dell06 ~]# kvm_stat
> kvm statistics
>
> efer_reload 0 0
> exits 11777822 258
> fpu_reload 158860 1
> halt_exits 931986 70
> halt_wakeup 70117 2
> host_state_reload 3780899 70
> hypercalls 0 0
> insn_emulation 5203509 178
> insn_emulation_fail 0 0
> invlpg 0 0
> io_exits 2580247 0
> irq_exits 1610751 8
> irq_injections 1930867 71
> irq_window 79641 0
> largepages 2501 0
> mmio_exits 183399 0
> mmu_cache_miss 604 0
> mmu_flooded 0 0
> mmu_pde_zapped 0 0
> mmu_pte_updated 0 0
> mmu_pte_write 1000 0
> mmu_recycled 0 0
> mmu_shadow_zapped 748 0
> mmu_unsync 0 0
> nmi_injections 0 0
> nmi_window 0 0
> pf_fixed 44196 0
> pf_guest 0 0
> remote_tlb_flush 519 0
> request_irq 0 0
> signal_exits 0 0
> tlb_flush 0 0
>
>
> Best Regards
>
> Hailong
next reply other threads:[~2012-05-16 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 12:11 Hailong Yang [this message]
2012-05-18 0:23 ` FW: Descriptions about KVM performance counters Marcelo Tosatti
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=4fb3996f.2c75440a.2bee.4d8b@mx.google.com \
--to=hailong.yang1115@gmail.com \
--cc=kvm@vger.kernel.org \
/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