From: Gerd Hoffmann <kraxel@redhat.com>
To: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: exits for no reason?
Date: Fri, 16 May 2008 10:09:31 +0200 [thread overview]
Message-ID: <482D413B.8050609@redhat.com> (raw)
Hi,
With xenner I see a very high number of exits for no appearent reason in
the statistics:
kvm stats : total diff
mmu_cache_miss : 5380 0
mmu_flooded : 1294 0
mmu_pde_zapped : 10132 0
mmu_pte_updated : 122292 0
mmu_pte_write : 128223 0
mmu_shadow_zapped : 4742 0
insn_emulation : 179971 1001
fpu_reload : 920 0
host_state_reload : 52192 1065
irq_exits : 52956 1226
halt_wakeup : 3302 0
halt_exits : 1770 0
io_exits : 41564 1001
exits : 12209733 454557
tlb_flush : 514163 2002
pf_guest : 80554 0
pf_fixed : 172032 0
Ideas what this might be? Unusual exit reason with no counter I guess?
Suggestions how to track that one down?
cheers,
Gerd
--
http://kraxel.fedorapeople.org/xenner/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
reply other threads:[~2008-05-16 8:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=482D413B.8050609@redhat.com \
--to=kraxel@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
/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