On Wed, Jun 04, 2008 at 01:49:41PM +0300, Avi Kivity wrote: >> >> Test is 1 million gettimeofday calls, Xeon 1.60GHz with 4MB L2. >> >> guest (qemu emulation): >> cycles:1189759332 >> >> guest (in-kernel emulation): >> cycles:628046412 >> >> guest (direct pmtimer): >> cycles:230372934 >> >> host (TSC): >> cycles:14862774 >> > > Ratio is 1:15:80 > > Looks like direct pmtimer is still quite slow. Are there any exits with > direct pmtimer, or is it all due to the ioport latency?
host (pmtimer): cycles:225768390 So its getting close-to-native performance. As you mentioned earlier, acpi_pm can't benefit from vsyscalls. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
