Il 03/09/2014 20:25, Chris J Arges ha scritto: > <snip> >> I'm not sure about the reason for the warp, but indeed the offset and >> uptime match (I'll check them against the trace tomorrow) so it's "just" >> that the VM's TSC base is not taken into account correctly. >> >> Can you gather another trace with the problematic patch reverted? >> >> Paolo >> > > Here is the third trace running with 0d3da0d2 reverted from the latest > kvm queue branch 11cc9ea3: > > http://people.canonical.com/~arges/kvm/trace-3.dat.xz
Thanks! And---yay!---I reproduced it on another machine. Paolo > $ uptime > 18:25:13 up 5 min, 1 user, load average: 0.21, 0.74, 0.44 > > qemu-system-x86_64 -enable-kvm -device pc-testdev -device > isa-debug-exit,iobase=0xf4,iosize=0x4 -display none -serial stdio > -device pci-testdev -kernel x86/kvmclock_test.flat -smp 2 --append > 10000000 1409768537 > enabling apic > enabling apic > kvm-clock: cpu 0, msr 0x:44e520 > kvm-clock: cpu 0, msr 0x:44e520 > Wallclock test, threshold 5 > Seconds get from host: 1409768537 > Seconds get from kvmclock: 1409768538 > Offset: 1 > Wallclock test, threshold 5 > Seconds get from host: 1409768537 > Seconds get from kvmclock: 1409768538 > Offset: 1 > Check the stability of raw cycle ... > Total vcpus: 2 > Test loops: 10000000 > Total warps: 0 > Total stalls: 0 > Worst warp: 0 > Raw cycle is stable > Monotonic cycle test: > Total vcpus: 2 > Test loops: 10000000 > Total warps: 0 > Total stalls: 0 > Worst warp: 0 > Measure the performance of raw cycle ... > Total vcpus: 2 > Test loops: 10000000 > TSC cycles: 1241970306 > Measure the performance of adjusted cycle ... > Total vcpus: 2 > Test loops: 10000000 > TSC cycles: 3266701026 > Return value from qemu: 1 > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
