On Wed, Feb 22, 2012 at 05:33:56PM +0100, David Cure wrote: > Le Sun, Feb 19, 2012 at 11:13:15AM +0200, Gleb Natapov ecrivait : > > > > > http://www.roullier.net/report-no-hpet.txt.gz > > > > > How have you acquired this trace? It does not trace all kvm events only > > those that have "set_irq" in them. > > I run : trace-cmd record -b 20000 -e kvm -P <process_pid> > Ah, I guess the reason is that it records events only of IO thread. You need to trace all vcpu threads too. Not sure trace-cmd allows more then one -P option though. > > Nothing particularly strange here. ~1745 IRQs are injected into the > > guest each second. RTC clock is configured to 1kH and other devices > > contribute ~721 irqs (MSI mostly) per second more. Hardly unusual. > > ok, so no ideas to decrease the response time ? > Without knowing the reason of the slowdown no. Probably you have the same problem as this other performance thread (frequent access to pm timer), but we need better trace to confirm that. -- Gleb. -- 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
