On Thu, Aug 19, 2010 at 10:07:19PM -1000, Zachary Amsden wrote: > The VMCB is reset whenever we receive a startup IPI, so Linux is setting > TSC back to zero happens very late in the boot process and destabilizing > the TSC. Instead, just set TSC to zero once at VCPU creation time. > > Why the separate patch? So git-bisect is your friend. > > Signed-off-by: Zachary Amsden <zamsden@xxxxxxxxxx> Shouldn't we set for whatever value the BSP already has, and then the BSP to zero? Since vcpus are initialized at different times, this pretty much guarantees that the guest will have desynchronized tsc at all cases (not that if it was better before...) -- 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
