On 8/27/2013 3:38 AM, Gleb Natapov wrote:
On Tue, Aug 27, 2013 at 09:18:00AM +0200, Paolo Bonzini wrote:
I've captured 20,000 lines of kvm trace output. This can be found
https://gist.github.com/devicenull/fa8f49d4366060029ee4/raw/fb89720d34b43920be22e3e9a1d88962bf305da8/trace
The guest is doing quite a lot of exits per second, mostly to (a) access
the ACPI timer
I see a lot of PM timer access not ACPI timer. The solution for that is
the patchset Brian linked.
(b) service NMIs. In fact, every NMI is reading the
timer too and causing an exit to QEMU.
Do you mean "kvm_exit: reason EXCEPTION_NMI rip 0xfffff800016dcf84 info
0 80000307"? Those are not NMIs, single NMI will kill Windows, they are #NM
exceptions. Brian, is your workload uses floating point calculation?
Yes, our workload uses floating point heavily. I'd also strongly
suspect it's doing various things with timers quite frequently. (This is
all third party software, so I don't have the source to examine to
determine exactly what it's doing).
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
